Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re^3: Introducing MooseX::hasn't

by Arunbear (Parson)
on Apr 03, 2012 at 10:23 UTC ( #963211=note: print w/ replies, xml ) Need Help??

in reply to Re^2: Introducing MooseX::hasn't
in thread Introducing MooseX::hasn't

It breaks the inheritance contract, not polymorphism per se (I think you've got the two concepts confused). Polymorphism doesn't depend on inheritance, e.g. Roles enable polymorphism without inheritance.

Comment on Re^3: Introducing MooseX::hasn't
Replies are listed 'Best First'.
Re^4: Introducing MooseX::hasn't
by tobyink (Abbot) on Apr 03, 2012 at 13:14 UTC

    No, polymorphism doesn't depend on inheritance, and I never claimed that it did. Polymorphism is generally an expected outcome of inheritance though. There are clearly other ways of allowing polymorphism though - roles as you say; also mocking, delegation, etc.

    perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
      From the POD:
      The idea behind polymorphism is that if Bar inherits from Foo, then I should be able to use an object of type Bar wherever I'd normally use Foo.
      That makes it sound like you're equating polymorphism with inheritance.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://963211]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (7)
As of 2015-10-14 05:26 GMT
Find Nodes?
    Voting Booth?

    Does Humor Belong in Programming?

    Results (320 votes), past polls