diff options
author | Dave Mitchell <davem@fdisolutions.com> | 2004-01-01 22:23:11 +0000 |
---|---|---|
committer | Dave Mitchell <davem@fdisolutions.com> | 2004-01-01 22:23:11 +0000 |
commit | 029f3b4481eb14b016dea8aa8fb43279a710daa3 (patch) | |
tree | 0f663a57a7014d8887743b8bd4d891d074a07fba /pod/perltoot.pod | |
parent | 53c33732a73c90e26f613c11afdc5110e6a919ff (diff) | |
download | perl-029f3b4481eb14b016dea8aa8fb43279a710daa3.tar.gz |
Document the quirks of SUPER, especially the fact that it it
relative to the current package and not to the invoking object.
p4raw-id: //depot/perl@22036
Diffstat (limited to 'pod/perltoot.pod')
-rw-r--r-- | pod/perltoot.pod | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perltoot.pod b/pod/perltoot.pod index 03372c7ae5..2497063877 100644 --- a/pod/perltoot.pod +++ b/pod/perltoot.pod @@ -940,7 +940,8 @@ comes to the rescue here. This way it starts looking in my class's @ISA. This only makes sense from I<within> a method call, though. Don't try to access anything in SUPER:: from anywhere else, because it doesn't exist outside -an overridden method call. +an overridden method call. Note that C<SUPER> refers to the superclass of +the current package, I<not> to the superclass of C<$self>. Things are getting a bit complicated here. Have we done anything we shouldn't? As before, one way to test whether we're designing |