Getting the stuff Timeless missed with his checkin for bug 106386

parent 4accb195
......@@ -7416,7 +7416,7 @@ TARGET="_top"
>, the perl documentation says that you should always use <TT
CLASS="function"
>binmode()</TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting <TT
CLASS="function"
>binmode()</TT
> at the beginning of the attachment files, there should be logic to determine if <TT
......@@ -17725,4 +17725,4 @@ NAME="zarro-boogs-found"
></DIV
></BODY
></HTML
>
\ No newline at end of file
>
......@@ -1246,10 +1246,10 @@ TARGET="_top"
>, the perl documentation says that you should always use <TT
CLASS="function"
>binmode()</TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting <TT
CLASS="function"
>binmode()</TT
> at the begining of the attachment files, there should be logic to determine if <TT
> at the beginning of the attachment files, there should be logic to determine if <TT
CLASS="function"
>binmode()</TT
> is needed or not.
......@@ -1632,4 +1632,4 @@ VALIGN="top"
></DIV
></BODY
></HTML
>
\ No newline at end of file
>
......@@ -1772,7 +1772,14 @@ binmode(STDOUT);
<note>
<para>
According to <ulink
url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>, the perl documentation says that you should always use <function>binmode()</function> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <function>binmode()</function> at the begining of the attachment files, there should be logic to determine if <function>binmode()</function> is needed or not.
url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>,
the perl documentation says that you should always use
<function>binmode()</function> when dealing with binary
files, but never when dealing with text files. That seems
to suggest that rather than arbitrarily putting
<function>binmode()</function> at the beginning of the
attachment files, there should be logic to determine if
<function>binmode()</function> is needed or not.
</para>
</note>
</step>
......
......@@ -2171,7 +2171,7 @@ binmode(STDOUT);
According to bug 62000, the perl documentation says that you should
always use binmode() when dealing with binary files, but never when
dealing with text files. That seems to suggest that rather than
aribtrarily putting binmode() at the beginning of the attachment files,
arbitrarily putting binmode() at the beginning of the attachment files,
there should be logic to determine if binmode() is needed or not.
Tip
......
......@@ -1772,7 +1772,14 @@ binmode(STDOUT);
<note>
<para>
According to <ulink
url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>, the perl documentation says that you should always use <function>binmode()</function> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <function>binmode()</function> at the begining of the attachment files, there should be logic to determine if <function>binmode()</function> is needed or not.
url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>,
the perl documentation says that you should always use
<function>binmode()</function> when dealing with binary
files, but never when dealing with text files. That seems
to suggest that rather than arbitrarily putting
<function>binmode()</function> at the beginning of the
attachment files, there should be logic to determine if
<function>binmode()</function> is needed or not.
</para>
</note>
</step>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment