in reply to How can I inherit from Bit::Vector?

Greetings,

Rather than going through all these hoops, why not just using containment?

AUTOLOAD makes it very easy to delegate to an inner Bit::Vector everything you do not care to intercept, so the difference from true inheritance is not much.
Cheers,
alf

You can't have everything: where would you put it?
  • Comment on Re: How can I inherit from Bit::Vector?

Replies are listed 'Best First'.
(tye)Re: How can I inherit from Bit::Vector?
by tye (Sage) on Nov 05, 2001 at 14:09 UTC

    One should only use inheritance on classes that were designed to be inheritted from. Bit::Vector appears to have not only not been designed to support inheritance, but actually designed to not support inheritance. So I agree that toma should stop fighting it.

    Plus inheritance is a bit of blunt weapon, especially in Perl. Unless you and/or Bit::Vector go out of your way to prevent it, (to take just one example) any non-method utility subroutines must be very carefully named (and Bit::Vector probably doesn't know about your names and so can't avoid accidentally using them in the next release).

    There is even a module on CPAN that makes dispatching the Bit::Vector method calls easy (sorry, I don't recall the name, though).

            - tye (in other words, "me too")
[reply]

In Section Seekers of Perl Wisdom