>, 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
></DIV
></BODY
></HTML
->
\ No newline at end of file
+>
>, 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.
></DIV
></BODY
></HTML
->
\ No newline at end of file
+>
<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>
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
<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>