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.
Re: Re: inheritance turns back and bites
Replies are listed 'Best First'.
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.