In perl.git, the branch yves/doc_hints has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/1510475f3ddac95b1e3fa2f23b7836a212cb6d7d?hp=8d417196984a5d4ca8786be90450a3c41389e7e1>
- Log -----------------------------------------------------------------
commit 1510475f3ddac95b1e3fa2f23b7836a212cb6d7d
Author: Yves Orton <demer...@gmail.com>
Date: Thu Jun 15 14:49:59 2017 +0200
improve hints hash docs as per leonerds suggestions
-----------------------------------------------------------------------
Summary of changes:
pod/perlvar.pod | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 2dba82618f..0857209b89 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -2167,11 +2167,13 @@ slot of the return of caller:
sub hints_hash { (caller(0))[10] }
-During compilation this hash may be used to store complex structures, such
-as code references, however once compilation is completed these structures
-will be flattened to a representation that accommodates only simple
-values, which means that complex structures such as references
-can not be retrieved at run-time via C<caller()> as described above.
+During compilation this hash may be used to store complex structures,
+such as code references, as well as simple non-referential scalars. A
+flattened copy of the values written into the hash is stored with the
+code that was compiled while it was in effect, and is the copy
+available via the C<caller()> mechanism. This copy preserves simple
+strings and numbers, but will not preserve more complex values
+like references.
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.
--
Perl5 Master Repository
