In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/8abccac8ff0df19277ea7cd5207ec52ac011a3b9?hp=aa121388b70a1669ae6ccf953787a0fc0c49752d>

- Log -----------------------------------------------------------------
commit 8abccac8ff0df19277ea7cd5207ec52ac011a3b9
Author: Andrew Rodland <[email protected]>
Date:   Tue Oct 12 07:27:23 2010 -0500

    Correct mistaken references to &PL_sv_true and &PL_sv false in perlguts
    
    Their correct names are &PL_sv_yes and &PL_sv_no.
-----------------------------------------------------------------------

Summary of changes:
 pod/perlguts.pod |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 104f27b..3a5f475 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -539,14 +539,14 @@ in restricted hashes. This caused such hash entries not 
to appear
 when iterating over the hash or when checking for the keys
 with the C<hv_exists> function.
 
-You can run into similar problems when you store C<&PL_sv_true> or
-C<&PL_sv_false> into AVs or HVs. Trying to modify such elements
+You can run into similar problems when you store C<&PL_sv_yes> or
+C<&PL_sv_no> into AVs or HVs. Trying to modify such elements
 will give you the following error:
 
     Modification of a read-only value attempted
 
 To make a long story short, you can use the special variables
-C<&PL_sv_undef>, C<&PL_sv_true> and C<&PL_sv_false> with AVs and
+C<&PL_sv_undef>, C<&PL_sv_yes> and C<&PL_sv_no> with AVs and
 HVs, but you have to make sure you know what you're doing.
 
 Generally, if you want to store an undefined value in an AV

--
Perl5 Master Repository

Reply via email to