summaryrefslogtreecommitdiff
path: root/pod/perlop.pod
diff options
context:
space:
mode:
authorYitzchak Scott-Thoennes <sthoenna@efn.org>2005-06-02 04:49:11 -0700
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2005-06-03 08:37:42 +0000
commitef191992665fc6763066d411ee6596d9638d260f (patch)
tree776bcc093fb17bd5449bf7c8897a8aade0c512bb /pod/perlop.pod
parentb464bac0b70c4876af1296864220315edde8461d (diff)
downloadperl-ef191992665fc6763066d411ee6596d9638d260f.tar.gz
Re: Should while ( <$fh> ) and while (< $fh >) do the same thing?
Message-ID: <20050602184911.GA3292@efn.org> p4raw-id: //depot/perl@24690
Diffstat (limited to 'pod/perlop.pod')
-rw-r--r--pod/perlop.pod3
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perlop.pod b/pod/perlop.pod
index b86dda4fba..04e1b48036 100644
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -1987,7 +1987,8 @@ depending on context. This distinction is determined on syntactic
grounds alone. That means C<< <$x> >> is always a readline() from
an indirect handle, but C<< <$hash{key}> >> is always a glob().
That's because $x is a simple scalar variable, but C<$hash{key}> is
-not--it's a hash element.
+not--it's a hash element. Even C<< <$x > >> (note the extra space)
+is treated as C<glob("$x ")>, not C<readline($x)>.
One level of double-quote interpretation is done first, but you can't
say C<< <$foo> >> because that's an indirect filehandle as explained