On Tuesday, August 27, 2002, at 12:46 , david wrote:
[..]
>
> thanks for the follow up and verify a ton of stuff. this is really nice.
> i don't totally understand your point a). can you provide your modules A.
> pm,
> B1.pm and C.pm? maybe that will clarify things a bit.
>
> david
well they hav
On Tue, Aug 27, 2002 at 10:28:25AM -0700, drieux wrote:
> Volks,
>
> am I just slow or what?
I wouldn't go that far ;-)
> but when I went to make the method in B1 that C would
> inherit to display the inheritence chain, I had thought
> I could likewise get away with the 'SUPER' trick a la
>
Drieux wrote:
>
> Hence one should only use SUPER in a method if
>
> a) the method itself is overriding an inherited method
> b) you have a clue that in multiple class inheritences
> you will find the one you really want?
>
>
>
> ciao
> drieux
>
> ---
thanks for the follow up and verify a
Volks,
am I just slow or what?
I liked david's illustration yesterday, and dashed off
this morning to code up the illustration about overridden
method - on the specific order of Connie's original concern,
so I had three packages A, B1, C - { base is to the left }.
So B1's overriding of A's ret
