functions (which is messy).
Firstly it forces the file handle to be considered binary at that
-point in the layer stack, i.e it turns off any CRLF translation.
+point in the layer stack, i.e. it turns off any CRLF translation.
Secondly in prevents the IO system seaching back before it in the
layer specification. This second effect is intended to disable other
taken as the name of the filehandle. Returns true on success,
C<undef> on failure.
-If DISCIPLINE is ommited the filehandle is made suitable for
-passing binary data. This includes turning off CRLF translation
-and marking it as bytes.
+If DISCIPLINE is omitted the filehandle is made suitable for passing
+binary data. This includes turning off possible CRLF translation and
+marking it as bytes (as opposed to Unicode characters).
On some systems (in general, DOS and Windows-based systems) binmode()
is necessary when you're not working with a text file. For the sake
The C<:bytes>, C<:crlf>, and C<:utf8>, and any other directives of the
form C<:...>, are called I/O I<disciplines>. The normal implementation
-of disciplines in perl5.8 and later is in terms of I<layers>. See
+of disciplines in Perl 5.8 and later is in terms of I<layers>. See
L<PerlIO>. (There is typically a one-to-one correspondence between
layers and disiplines.) The C<open> pragma can be used to establish
default I/O disciplines. See L<open>.