summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-04-26 03:21:50 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-04-26 03:21:50 +0000
commit5387ccf1031d2986d79b744c0c632d1e89cf4d3e (patch)
tree0877db99e0e6f7d4c08297e53724dca29c1b7e0c /pod
parent827a599d60f0d355fc1cd4922bbb1edec4849a02 (diff)
downloadperl-5387ccf1031d2986d79b744c0c632d1e89cf4d3e.tar.gz
Add an idea/question from Damian.
p4raw-id: //depot/perl@16179
Diffstat (limited to '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 e715a6145a..60be5b9c2f 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -542,6 +542,12 @@ 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?
+
=head1 Vague ideas
Ideas which have been discussed, and which may or may not happen.