summaryrefslogtreecommitdiff
path: root/pod/perltodo.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-04-26 23:56:32 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-04-26 23:56:32 +0000
commitcbda53d5630fb826c2d06e07763221ee90547c7b (patch)
tree131b285a674f2fec9065bf2214b77cf9758aafd1 /pod/perltodo.pod
parent67627c52ebaff7c8807f003541daf98ec69bc00b (diff)
downloadperl-cbda53d5630fb826c2d06e07763221ee90547c7b.tar.gz
Add taint rethink to the todo list.
p4raw-id: //depot/perl@16205
Diffstat (limited to 'pod/perltodo.pod')
-rw-r--r--pod/perltodo.pod6
1 files changed, 6 insertions, 0 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 60be5b9c2f..0a6b8e1596 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -548,6 +548,12 @@ 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.