diff options
| author | Lukas Mai <l.mai@web.de> | 2016-06-11 12:40:42 +0200 |
|---|---|---|
| committer | Lukas Mai <l.mai@web.de> | 2016-06-11 12:40:42 +0200 |
| commit | 5a0de58193409bae1e4b2ebb59c6d1af2c9b4f00 (patch) | |
| tree | f15321e436a9358bd44b7a16820fd6f13552e99a /pod/perlport.pod | |
| parent | 016af03917eea80cc676de5e934ea517073e5976 (diff) | |
| download | perl-5a0de58193409bae1e4b2ebb59c6d1af2c9b4f00.tar.gz | |
pod/*: remove deprecated L<"section"> and L<section> syntax
Diffstat (limited to 'pod/perlport.pod')
| -rw-r--r-- | pod/perlport.pod | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/pod/perlport.pod b/pod/perlport.pod index 15d411c8eb..ffabf07182 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -67,9 +67,9 @@ The important thing is to decide where the code will run and to be deliberate in your decision. The material below is separated into three main sections: main issues of -portability (L<"ISSUES">), platform-specific issues (L<"PLATFORMS">), and +portability (L</"ISSUES">), platform-specific issues (L</"PLATFORMS">), and built-in Perl functions that behave differently on various ports -(L<"FUNCTION IMPLEMENTATIONS">). +(L</"FUNCTION IMPLEMENTATIONS">). This information should not be considered complete; it includes possibly transient information about idiosyncrasies of some of the ports, almost @@ -743,7 +743,7 @@ For those times when it is necessary to have platform-specific code, consider keeping the platform-specific code in one place, making porting to other platforms easier. Use the C<Config> module and the special variable C<$^O> to differentiate platforms, as described in -L<"PLATFORMS">. +L</"PLATFORMS">. Beware of the "else syndrome": @@ -892,7 +892,7 @@ scripts such as I<pl2bat.bat> or I<pl2cmd> to put wrappers around your scripts. Newline (C<\n>) is translated as C<\015\012> by STDIO when reading from -and writing to files (see L<"Newlines">). C<binmode(FILEHANDLE)> +and writing to files (see L</"Newlines">). C<binmode(FILEHANDLE)> will keep C<\n> translated as C<\012> for that filehandle. Since it is a no-op on other systems, C<binmode> should be used for cross-platform code that deals with binary data. That's assuming you realize in advance @@ -1217,7 +1217,7 @@ an effect on what happens with some Perl functions (such as C<chr>, C<pack>, C<print>, C<printf>, C<ord>, C<sort>, C<sprintf>, C<unpack>), as well as bit-fiddling with ASCII constants using operators like C<^>, C<&> and C<|>, not to mention dealing with socket interfaces to ASCII computers -(see L<"Newlines">). +(see L</"Newlines">). Fortunately, most web servers for the mainframe will correctly translate the C<\n> in the following statement to its ASCII equivalent |