From: Rafael Garcia-Suarez Date: Mon, 22 May 2006 13:47:19 +0000 (+0000) Subject: More nits in perlpragma, and remove the warning about %^H being X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=46e5f5f47696caa998bfcb1e374d29f888f44b9b;p=p5sagit%2Fp5-mst-13.2.git More nits in perlpragma, and remove the warning about %^H being strictly internal in perlvar. p4raw-id: //depot/perl@28271 --- diff --git a/pod/perlpragma.pod b/pod/perlpragma.pod index 9c4fd2b..3bdf8b7 100644 --- a/pod/perlpragma.pod +++ b/pod/perlpragma.pod @@ -115,12 +115,14 @@ and C is Hence the C and C routines are called at B for the user's code. -User pragmata store their state by writing to C<%^H>, hence these two -routines manipulate C<%^H>. The state information in C<%^H> is stored in the -optree, and can be retrieved at runtime with C, at index 10 of the -list of returned results. In the example pragma, retrieval is encapsulated -into the routine C. This uses C to determine the -state of C<$^H{myint}> when each line of the user's script was called, and +User pragmata store their state by writing to the magical hash C<%^H>, +hence these two routines manipulate it. The state information in C<%^H> is +stored in the optree, and can be retrieved at runtime with C, at +index 10 of the list of returned results. In the example pragma, retrieval +is encapsulated into the routine C, which takes as parameter +the number of call frames to go up to find the value of the pragma in the +user's script. This uses C to determine the value of +C<$^H{myint}> when each line of the user's script was called, and therefore provide the correct semantics in the subroutine implementing the overloaded addition. diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 8552274..68c8303 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -995,11 +995,8 @@ version of the same lexical pragma: =item %^H -WARNING: This variable is strictly for internal use only. Its availability, -behavior, and contents are subject to change without notice. - The %^H hash provides the same scoping semantic as $^H. This makes it -useful for implementation of lexically scoped pragmas. +useful for implementation of lexically scoped pragmas. See L. =item $INPLACE_EDIT