Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

Re: inheritance turns back and bites

by borisz (Canon)
on Mar 01, 2004 at 13:28 UTC ( #332887=note: print w/replies, xml ) Need Help??

in reply to inheritance turns back and bites

you expect that increment call SomeData::add, but it calls MyNumber::add. Because it is a MyNumber object. If you do not want that, write in package SomeData
sub increment { my $self = shift; $self->SomeData::add(number => 1); }

Replies are listed 'Best First'.
Re: Re: inheritance turns back and bites
by esskar (Deacon) on Mar 01, 2004 at 13:46 UTC
    Always use SUPER instead of the parent-class-name; so in the case of changeing the parent-class, you won't have to replace all the "SomeData::" stuff to the new parent-class-name.
    SUPER is pretty super.
      But SUPER is wrong here, I like to use SomeData or build something with __PACKAGE__.
        If your intent is to ensure that increment calls add in the same package, why not use:
        sub increment { my $self = shift; &add($self, number => 1); }
        Use subroutine calls when you want to create your own explicit binding, use -> notation when you desire runtime binding of the message.

        Of course, it would be my opinion that it is particularly bad form for a child class to re-implement a method in a manner that is not backward compatible - it's a violation of the contract as far as I'm concerned.

        --Toby Ovod-Everett

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://332887]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2018-02-22 01:46 GMT
Find Nodes?
    Voting Booth?
    When it is dark outside I am happiest to see ...

    Results (288 votes). Check out past polls.