summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
Diffstat (limited to 'pod')
-rw-r--r--pod/perlapi.pod2
-rw-r--r--pod/perlintern.pod2
2 files changed, 3 insertions, 1 deletions
diff --git a/pod/perlapi.pod b/pod/perlapi.pod
index 3ea050e943..5cdc152387 100644
--- a/pod/perlapi.pod
+++ b/pod/perlapi.pod
@@ -4631,6 +4631,8 @@ Found in file sv.h
X<SvUTF8>
Returns a boolean indicating whether the SV contains UTF-8 encoded data.
+Call this after SvPV() in case any call to string overloading updates the
+internal flag.
bool SvUTF8(SV* sv)
diff --git a/pod/perlintern.pod b/pod/perlintern.pod
index 5c901cd47d..785a36a3f6 100644
--- a/pod/perlintern.pod
+++ b/pod/perlintern.pod
@@ -621,7 +621,7 @@ in PL_op->op_targ), wasting a name SV for them doesn't make sense.
The SVs in the names AV have their PV being the name of the variable.
NV+1..IV inclusive is a range of cop_seq numbers for which the name is
valid. For typed lexicals name SV is SVt_PVMG and SvSTASH points at the
-type. For C<our> lexicals, the type is also SVt_PVGV, with the MAGIC slot
+type. For C<our> lexicals, the type is also SVt_PVMG, with the OURSTASH slot
pointing at the stash of the associated global (so that duplicate C<our>
declarations in the same package can be detected). SvCUR is sometimes
hijacked to store the generation number during compilation.