[PATCH] pod/perlvar.pod

Even though $* is deprecated, I got bitten by the fact that its
documentation wasn't entirely accurate. (No, I didn't use $* myself).

Here's a doc-patch (against bleedperl).


Abigail


*** pod/perlvar.pod.orig	Tue Jan 23 01:20:38 2001
--- pod/perlvar.pod	Tue Jan 23 01:33:28 2001
***************
*** 193,208 ****
  
  =item $*
  
! Set to 1 to do multi-line matching within a string, 0 to tell Perl
! that it can assume that strings contain a single line, for the purpose
! of optimizing pattern matches.  Pattern matches on strings containing
! multiple newlines can produce confusing results when C<$*> is 0.  Default
! is 0.  (Mnemonic: * matches multiple things.)  This variable
! influences the interpretation of only C<^> and C<$>.  A literal newline can
! be searched for even when C<$* == 0>.
  
  Use of C<$*> is deprecated in modern Perl, supplanted by 
  the C</s> and C</m> modifiers on pattern matching.
  
  =item input_line_number HANDLE EXPR
  
--- 193,213 ----
  
  =item $*
  
! Set to a non-zero integer value to do multi-line matching within a
! string, 0 (or undefined) to tell Perl that it can assume that strings
! contain a single line, for the purpose of optimizing pattern matches.
! Pattern matches on strings containing multiple newlines can produce
! confusing results when C<$*> is 0 or undefined. Default is undefined.
! (Mnemonic: * matches multiple things.) This variable influences the
! interpretation of only C<^> and C<$>. A literal newline can be searched
! for even when C<$* == 0>.
  
  Use of C<$*> is deprecated in modern Perl, supplanted by 
  the C</s> and C</m> modifiers on pattern matching.
+ 
+ Assigning a non-numerical value to C<$*> triggers a warning (and makes
+ C<$*> act if C<$* == 0>), while assigning a numerical value to C<$*>
+ makes that an implicite C<int> is applied on the value.
  
  =item input_line_number HANDLE EXPR
  

• [PATCH] pod/perlvar.pod by abigail
• Re: [PATCH] pod/perlvar.pod by Jarkko Hietaniemi