From: M. J. T. Guy Date: Mon, 12 Jun 2000 14:55:59 +0000 (+0100) Subject: Re: [ID 20000612.001] map {chop; $_} (Literals problem) X-Git-Tag: accepted/trunk/20130322.191538~34778^2~61 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e5dd471a14b6158556f6371bc9fc9576e5189864;p=platform%2Fupstream%2Fperl.git Re: [ID 20000612.001] map {chop; $_} (Literals problem) Message-Id: p4raw-id: //depot/cfgperl@6277 --- diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 25269d4..78a6318 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -2078,9 +2078,9 @@ or equivalently, @foo = grep {!/^#/} @bar; # weed out comments -Note that, because C<$_> is a reference into the list value, it can -be used to modify the elements of the array. While this is useful and -supported, it can cause bizarre results if the LIST is not a named array. +Note that C<$_> is an alias to the list value, so it can be used to +modify the elements of the LIST. While this is useful and supported, +it can cause bizarre results if the elements of LIST are not variables. Similarly, grep returns aliases into the original list, much as a for loop's index variable aliases the list elements. That is, modifying an element of a list returned by grep (for example, in a C, C @@ -2462,9 +2462,9 @@ is just a funny way to write $hash{getkey($_)} = $_; } -Note that, because C<$_> is a reference into the list value, it can -be used to modify the elements of the array. While this is useful and -supported, it can cause bizarre results if the LIST is not a named array. +Note that C<$_> is an alias to the list value, so it can be used to +modify the elements of the LIST. While this is useful and supported, +it can cause bizarre results if the elements of LIST are not variables. Using a regular C loop for this purpose would be clearer in most cases. See also L for an array composed of those items of the original list for which the BLOCK or EXPR evaluates to true.