From: Nicholas Clark <nick@ccl4.org>
Date: Sun, 1 Jul 2007 12:33:39 +0000 (+0000)
Subject: Add some information to the comments describing SV flag bits.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2e9f07a2fdf1a2d5a1f1e89b37d3b33b32ed2a72;p=p5sagit%2Fp5-mst-13.2.git

Add some information to the comments describing SV flag bits.

p4raw-id: //depot/perl@31512
---

diff --git a/sv.h b/sv.h
index 8ad522d..c5b0179 100644
--- a/sv.h
+++ b/sv.h
@@ -344,15 +344,20 @@ perform the upgrade if necessary.  See C<svtype>.
 #define PRIVSHIFT 4	/* (SVp_?OK >> PRIVSHIFT) == SVf_?OK */
 
 #define SVf_AMAGIC	0x10000000  /* has magical overloaded methods */
+
+/* Ensure this value does not clash with the GV_ADD* flags in gv.h: */
 #define SVf_UTF8        0x20000000  /* SvPV is UTF-8 encoded
 				       This is also set on RVs whose overloaded
 				       stringification is UTF-8. This might
 				       only happen as a side effect of SvPV() */
 					   
-/* Ensure this value does not clash with the GV_ADD* flags in gv.h */
 
 /* Some private flags. */
 
+/* PVAV could probably use 0x2000000 without conflict. I assume that PVFM can
+   be UTF-8 encoded, and PVCVs could well have UTF-8 prototypes. PVIOs haven't
+   been restructured, so sometimes get used as string buffers.  */
+
 /* PVHV */
 #define SVphv_SHAREKEYS 0x20000000  /* PVHV keys live on shared string table */
 /* PVNV, PVMG, presumably only inside pads */