diff options
| author | Peter Prymmer <PPrymmer@factset.com> | 2001-01-29 08:46:25 -0800 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2001-01-30 00:56:47 +0000 |
| commit | 11e1c8f2799d09ead03e234a9f91269f8b6b179b (patch) | |
| tree | e5829a4fc048b11cb9f6a06f89563fda35bf3230 /pod/perliol.pod | |
| parent | 565c2591423801356441fb78477c26068ed4f07c (diff) | |
| download | perl-11e1c8f2799d09ead03e234a9f91269f8b6b179b.tar.gz | |
pod problems in io
Message-ID: <Pine.OSF.4.10.10101291636420.230748-100000@aspara.forte.com>
p4raw-id: //depot/perl@8593
Diffstat (limited to 'pod/perliol.pod')
| -rw-r--r-- | pod/perliol.pod | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/pod/perliol.pod b/pod/perliol.pod index fc8f923063..ac6a4a221c 100644 --- a/pod/perliol.pod +++ b/pod/perliol.pod @@ -62,8 +62,8 @@ scalar's type changes.) An IO stream is then in general represented as a pointer to this linked-list of "layers". It should be noted that because of the double indirection in a C<PerlIO *>, -a C<< &(perlio->next) >> "is" a C<PerlIO *>, and so to some degree at least -one layer can use the "standard" API on the next layer down. +a C<< &(perlio-E<gt>next) >> "is" a C<PerlIO *>, and so to some degree +at least one layer can use the "standard" API on the next layer down. A "layer" is composed of two parts: @@ -246,9 +246,9 @@ All writes should be appends. =item PERLIO_F_CRLF -Layer is performing Win32-like "\n" => CR,LF for output and CR,LF => -"\n" for input. Normally the provided "crlf" layer is the only layer -that need bother about this. C<PerlIO_binmode()> will mess with this +Layer is performing Win32-like "\n" mapped to CR,LF for output and CR,LF +mapped to "\n" for input. Normally the provided "crlf" layer is the only +layer that need bother about this. C<PerlIO_binmode()> will mess with this flag rather than add/remove layers if the C<PERLIO_K_CANCRLF> bit is set for the layers class. |