diff options
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perlapio.pod | 9 | ||||
| -rw-r--r-- | pod/perliol.pod | 10 |
2 files changed, 9 insertions, 10 deletions
diff --git a/pod/perlapio.pod b/pod/perlapio.pod index 6f0c96cb17..06e3d14e62 100644 --- a/pod/perlapio.pod +++ b/pod/perlapio.pod @@ -136,7 +136,7 @@ There may be an implementation limit on the number of open handles, which may be lower than the limit on the number of open files - C<errno> may not be set when C<NULL> is returned if this limnit is exceeded. -=item B<PerlIO_reopen(path,mode,f) +=item B<PerlIO_reopen(path,mode,f)> While this currently exists in all three implementations perl itself does not use it. I<As perl does not use it, it is not well tested.> @@ -389,7 +389,7 @@ Do not use this - use PerlIO_fast_gets. Obscure - set count of bytes in the buffer. Deprecated. Only usable if PerlIO_canset_cnt() returns true. -Currently used in only doio.c to force count < -1 to -1. +Currently used in only doio.c to force count less than -1 to -1. Perhaps should be PerlIO_set_empty or similar. This call may actually do nothing if "count" is deduced from pointer and a "limit". @@ -433,9 +433,9 @@ B<ptype> is perl's charcter for the kind of IO: =over 8 -=item '<' read +=item 'E<lt>' read -=item '>' write +=item 'E<gt>' write =item '+' read/write @@ -468,7 +468,6 @@ recursively call PerlIO and be a problem. PerlIO_debug writes to the file named by $ENV{'PERLIO_DEBUG'} typical use might be - Bourne shells: PERLIO_DEBUG=/dev/tty ./perl somescript some args 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. |