X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlvar.pod;h=68573e3d498177d17ea7c4236bf8c77253704f81;hb=b8921b3e20c463c85c5db53a08af87e03d44b1d3;hp=7f655900239dfd12b7ee668b1ab64e4ab6f31e85;hpb=db1511c850bfe94373082caa16c1f91ab1ce8510;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 7f65590..68573e3 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -58,14 +58,14 @@ the change may affect other modules which rely on the default values of the special variables that you have changed. This is one of the correct ways to read the whole file at once: - open my $fh, "foo" or die $!; + open my $fh, "<", "foo" or die $!; local $/; # enable localized slurp mode my $content = <$fh>; close $fh; But the following code is quite bad: - open my $fh, "foo" or die $!; + open my $fh, "<", "foo" or die $!; undef $/; # enable slurp mode my $content = <$fh>; close $fh; @@ -81,7 +81,7 @@ inside some short C<{}> block, you should create one yourself. For example: my $content = ''; - open my $fh, "foo" or die $!; + open my $fh, "<", "foo" or die $!; { local $/; $content = <$fh>; @@ -150,10 +150,11 @@ don't use it: The following functions: -abs, alarm, chomp chop, chr, chroot, cos, defined, eval, exp, glob, -hex, int, lc, lcfirst, length, log, lstat, mkdir, ord, pos, print, -quotemeta, readlink, readpipe, ref, require, reverse, rmdir, sin, split, -sqrt, stat, study, uc, ucfirst, unlink, unpack. +abs, alarm, chomp, chop, chr, chroot, cos, defined, eval, exp, glob, +hex, int, lc, lcfirst, length, log, lstat, mkdir, oct, ord, pos, print, +quotemeta, readlink, readpipe, ref, require, reverse (in scalar context only), +rmdir, sin, split (on its second argument), sqrt, stat, study, uc, ucfirst, +unlink, unpack. =item * @@ -163,8 +164,8 @@ See L =item * -The pattern matching operations C, C, and C when used -without an C<=~> operator. +The pattern matching operations C, C and C (aka C) +when used without an C<=~> operator. =item * @@ -442,7 +443,7 @@ instead of lines, with the maximum record size being the referenced integer. So this: local $/ = \32768; # or \"32768", or \$var_containing_32768 - open my $fh, $myfile or die $!; + open my $fh, "<", $myfile or die $!; local $_ = <$fh>; will read a record of no more than 32768 bytes from FILE. If you're @@ -478,7 +479,8 @@ buffered otherwise. Setting this variable is useful primarily when you are outputting to a pipe or socket, such as when you are running a Perl program under B and want to see the output as it's happening. This has no effect on input buffering. See L -for that. (Mnemonic: when you want your pipes to be piping hot.) +for that. See L on how to select the output channel. +See also L. (Mnemonic: when you want your pipes to be piping hot.) =item IO::Handle->output_field_separator EXPR @@ -789,7 +791,7 @@ variable, or in other words, if a system or library call fails, it sets this variable. This means that the value of C<$!> is meaningful only I after a B: - if (open(FH, $filename)) { + if (open my $fh, "<", $filename) { # Here $! is meaningless. ... } else { @@ -1215,7 +1217,8 @@ Debug subroutine enter/exit. =item 0x02 -Line-by-line debugging. +Line-by-line debugging. Causes DB::DB() subroutine to be called for each +statement executed. Also causes saving source code lines (like 0x400). =item 0x04 @@ -1252,12 +1255,13 @@ were compiled. =item 0x400 -Debug assertion subroutines enter/exit. +Save source code lines into C<@{"_<$filename"}>. =back Some bits may be relevant at compile-time only, some at run-time only. This is a new mechanism and the details may change. +See also L. =item $LAST_REGEXP_CODE_RESULT