summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChip Salzenberg <chip@pobox.com>2011-05-16 08:34:27 -0700
committerChip Salzenberg <chip@pobox.com>2011-05-16 08:34:27 -0700
commitefca99a9a1e53d71970eb6f816ed177a1b5c774f (patch)
tree38c319c8b620a3276d3c5b05f6e4cfa799475e36
parent0fa493bca1146fc79e7b4ff31c6b7cbac165dd6e (diff)
downloadperl-efca99a9a1e53d71970eb6f816ed177a1b5c774f.tar.gz
clarify *foo{IO} doc
-rw-r--r--pod/perlref.pod11
1 files changed, 6 insertions, 5 deletions
diff --git a/pod/perlref.pod b/pod/perlref.pod
index 550f4c14d2..5b5033de7e 100644
--- a/pod/perlref.pod
+++ b/pod/perlref.pod
@@ -74,11 +74,12 @@ reference that the backslash returned. Here are some examples:
$coderef = \&handler;
$globref = \*foo;
-It isn't possible to create a true reference to an IO handle (filehandle
-or dirhandle) using the backslash operator. The most you can get is a
-reference to a typeglob, which is actually a complete symbol table entry.
-But see the explanation of the C<*foo{THING}> syntax below. However,
-you can still use type globs and globrefs as though they were IO handles.
+Using the backslash operator, you can't create a true reference to an IO
+handle (filehandle plus dirhandle). You can do it with the C<*foo{THING}>
+syntax, described below. Using the backslash, the closest you can get is a
+reference to a typeglob (a complete symbol table entry). For historical
+reasons, if you use a glob as an IO handle, Perl uses the IO handle inside
+the glob, so this is usually good enough.
=item 2.
X<array, anonymous> X<[> X<[]> X<square bracket>