in reply to use of modules in special cases
No, you should not use B;.
Child classes B1 and B2 handle all aspects of their inheritance from B. You should not need to use B unless you specifically want a B object.
There are a lot of strategies for ensuring that B1 and B2 implement the full interface needed for them to be treated polymorphically as children of B. Role as interfaces, pure-virtual base classes (not as common in Perl), base classes that throw exceptions if an accessor is called without having been overridden in a base, and others.
Dave
|
---|
In Section
Seekers of Perl Wisdom