[DOCPATCH] perlguts.pod: fix the names of the true/false values

From cdb960b7a2febb788f61a3fb237c04ea27b4ed81 Mon Sep 17 00:00:00 2001
From: Andrew Rodland <arodland@cpan.org>
Date: Tue, 12 Oct 2010 07:27:23 -0500
Subject: [PATCH] Correct mistaken references to &PL_sv_true and &PL_sv false in perlguts

Their correct names are &PL_sv_yes and &PL_sv_no.
---
 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
-- 
1.7.1

• [DOCPATCH] perlguts.pod: fix the names of the true/false values by Andrew Rodland
• Re: [DOCPATCH] perlguts.pod: fix the names of the true/false values by Florian Ragwitz