The array C<@ARGV> contains the command-line arguments intended for
the script. C<$#ARGV> is generally the number of arguments minus
one, because C<$ARGV[0]> is the first argument, I<not> the program's
-command name itself. See C<$0> for the command name.
+command name itself. See L</$0> for the command name.
=item ARGV
X<ARGV>
Non-VMS systems do normal I/O, so it's safe to mix record and
non-record reads of a file.
-See also L<perlport/"Newlines">. Also see C<$.>.
+See also L<perlport/"Newlines">. Also see L</$.>.
Mnemonic: / delimits line boundaries when quoting poetry.
F</cdrom/install> fails. The upper eight bits reflect specific error
conditions encountered by the program (the program's C<exit()> value).
The lower eight bits reflect mode of failure, like signal death and
-core dump information. See C<wait(2)> for details. In contrast to
+core dump information. See L<wait(2)> for details. In contrast to
C<$!> and C<$^E>, which are set only if error condition is detected,
the variable C<$?> is set on each C<wait> or pipe C<close>,
overwriting the old value. This is more like C<$@>, which on every
=item $]
X<$]> X<$OLD_PERL_VERSION>
-See C<$^V> for a more modern representation of the Perl version that allows
+See L</$^V> for a more modern representation of the Perl version that allows
accurate string comparisons.
The version + patchlevel / 1000 of the Perl interpreter. This variable
Unicode::Semantics
Unicode::Unihan
unzip(1)
+wait(2)
waitpid(3)
wget(1)
Win32::Locale
pod/perluniintro.pod Verbatim line length including indents exceeds 80 by 3
pod/perluniprops.pod =item type mismatch 6
pod/perlutil.pod ? Should you be using L<...> instead of 1
-pod/perlvar.pod ? Should you be using L<...> instead of 4
pod/perlvar.pod Verbatim line length including indents exceeds 80 by 9
pod/perlvms.pod ? Should you be using F<...> or maybe L<...> instead of 1
pod/perlvms.pod ? Should you be using L<...> instead of 1