Note that PVIOs probably aren't worth shrinking. Note 3 possible

subflags for -C if the two Unicode TODOs are done.

p4raw-id: //depot/perl@27872

2 files changed, 10 insertions, 3 deletions

diff --git a/pod/perlrun.pod b/pod/perlrun.pod
index ee35b11bb0..b973779437 100644
--- a/pod/perlrun.pod
+++ b/pod/perlrun.pod
@@ -315,6 +315,10 @@ are as follows; listing the letters is equal to summing the numbers.
               of decreasing precedence) -- if the variables indicate
               UTF-8, then the selected "IOEioA" are in effect
 
+=for todo
+perltodo mentions Unicode in %ENV and filenames. I guess that these will be
+options e and f (or F).
+
 For example, C<-COE> and C<-C6> will both turn on UTF-8-ness on both
 STDOUT and STDERR.  Repeating letters is just redundant, not cumulative
 nor toggling.
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 83af8fe5c5..4582de83ca 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -427,11 +427,14 @@ These tasks would need C knowledge, and roughly the level of knowledge of
 the perl API that comes from writing modules that use XS to interface to
 C.
 
-=head2 shrink C<IO>s
+=head2 shrink C<PVBM>s
 
 By removing unused elements and careful re-ordering, the structures for C<AV>s,
-C<HV>s, C<CV>s and C<GV>s have recently been shrunk considerably. C<PVIO>s and
-C<PVBM>s might have some savings to win.
+C<HV>s, C<CV>s and C<GV>s have recently been shrunk considerably. C<PVIO>s
+probably aren't worth it, as typical programs don't use more than 8, and
+(at least) C<Filter::Util::Call> uses C<SvPVX>/C<SvCUR>/C<SvLEN> on a C<PVIO>,
+so it would mean code changes to modules on CPAN. C<PVBM>s might have some
+savings to win.
 
 =head2 Implicit Latin 1 => Unicode translation