[Patch] perlapio.pod

[p5sagit/p5-mst-13.2.git] / pod / perltodo.pod

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 0ed8d64..0a6b8e1 100644 (file)
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -94,12 +94,12 @@ to another single Unicode character.  See lib/unicore/SpecCase.txt
 
 =item *
 
-UTF-8 identifier names should probably be canonized: NFC?
+UTF-8 identifier names should probably be canonicalized: NFC?
 
 =item *
 
 UTF-8 in package names and sub names?  The first is problematic
-because of the mapping to pathnames, ditto for the second one is
+because of the mapping to pathnames, ditto for the second one if
 one does autosplitting, for example.
 
 =back
@@ -107,7 +107,7 @@ one does autosplitting, for example.
 See L<perlunicode/UNICODE REGULAR EXPRESSION SUPPORT LEVEL> for what's
 there and what's missing.  Almost all of Levels 2 and 3 is missing,
 and as of 5.8.0 not even all of Level 1 is there.
-They have some tricks Perl doesn't yet implement like character
+They have some tricks Perl doesn't yet implement, such as character
 class subtraction.
 
        http://www.unicode.org/unicode/reports/tr18/
@@ -542,6 +542,18 @@ even with the same keys.
 This should be allowed if the new keyset is a subset of the old
 keyset.  May require more extra code than we'd like in pp_aassign.
 
+=head2 Should overload be inheritable?
+
+Should overload be 'contagious' through @ISA so that derived classes
+would inherit their base classes' overload definitions?  What to do
+in case of overload conflicts?
+
+=head2 Taint rethink
+
+Should taint be stopped from affecting control flow, if ($tainted)?
+Should tainted symbolic method calls and subref calls be stopped?
+(Look at Ruby's $SAFE levels for inspiration?)
+
 =head1 Vague ideas
 
 Ideas which have been discussed, and which may or may not happen.