summaryrefslogtreecommitdiff
path: root/pod/perlvar.pod
diff options
context:
space:
mode:
authorLukas Mai <lukasmai.403@gmail.com>2023-03-28 09:14:35 +0200
committerYves Orton <demerphq@gmail.com>2023-03-28 17:34:46 +0800
commit19151286d6e3fc6fd8238e85d78ea74f2cae3cc8 (patch)
tree73102fb2d5e57a19160d8d0a8f00646917bafd27 /pod/perlvar.pod
parent095fd90e6ff7791c309ef4175edebb2295e5ea04 (diff)
downloadperl-19151286d6e3fc6fd8238e85d78ea74f2cae3cc8.tar.gz
[doc] update description of $^H and %^H in perlvar
- remove trailing spaces - add hyperlink to "caller" in perlfunc - add hyperlink to $^H in description of %^H - change "pointers to objects" to "references to objects" - change "semantic" to "semantics" - reword "useful for implementation of pragmas" as "useful for implementing pragmas"
Diffstat (limited to 'pod/perlvar.pod')
-rw-r--r--pod/perlvar.pod17
1 files changed, 8 insertions, 9 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index abbfc50ca8..54d2be32d2 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -747,7 +747,7 @@ The C<$SIG{__DIE__}> hook is called even inside an C<eval()>. It was
never intended to happen this way, but an implementation glitch made
this possible. This used to be deprecated, as it allowed strange action
at a distance like rewriting a pending exception in C<$@>. Plans to
-rectify this have been scrapped, as users found that rewriting a
+rectify this have been scrapped, as users found that rewriting a
pending exception is actually a useful feature, and not a bug.
The C<$SIG{__DIE__}> doesn't support C<'IGNORE'>; it has the same
@@ -1739,7 +1739,7 @@ Suppose we wrote the following string to a file:
$string .= "epsilon zeta eta\n\n";
$string .= "theta\n";
- my $file = 'simple_file.txt';
+ my $file = 'simple_file.txt';
open my $OUT, '>', $file or die;
print $OUT $string;
close $OUT or die;
@@ -2368,7 +2368,7 @@ value when the interpreter started to compile the BLOCK.
Each time a statement completes being compiled, the current value of
C<$^H> is stored with that statement, and can later be retrieved via
-C<(caller($level))[8]>.
+C<(caller($level))[8]>. See L<perlfunc/caller EXPR>.
When perl begins to parse any block construct that provides a lexical scope
(e.g., eval body, required file, subroutine body, loop body, or conditional
@@ -2412,15 +2412,14 @@ This variable was added in Perl 5.003.
=item %^H
X<%^H>
-The C<%^H> hash provides the same scoping semantic as C<$^H>. This makes
-it useful for implementation of lexically scoped pragmas. See
-L<perlpragma>. All the entries are stringified when accessed at
-runtime, so only simple values can be accommodated. This means no
-pointers to objects, for example.
+The C<%^H> hash provides the same scoping semantics as L<C<$^H>|/$^H>. This
+makes it useful for implementing lexically scoped pragmas. See L<perlpragma>.
+All the entries are stringified when accessed at runtime, so only simple values
+can be accommodated. This means no references to objects, for example.
Each time a statement completes being compiled, the current value of
C<%^H> is stored with that statement, and can later be retrieved via
-C<(caller($level))[10]>.
+C<(caller($level))[10]>. See L<perlfunc/caller EXPR>.
When putting items into C<%^H>, in order to avoid conflicting with other
users of the hash there is a convention regarding which keys to use.