Is Class::SelfMethods superceded by C::P then?
So I bite the bullet, start using it, and suddenly everything starts clearing up.
I had the same feeling when I started using a really lightweight, prototype-based configuration. All these objects that would've needed either many parameters, tweaking the minute details of their behaviour or a lasagne layers of overrideable methods suddenly became simple, clear and 100% adaptable.
That experience got me reading about Self, JavaScript and the various Perl modules. I think I'm already sold.
Brad
PS. I'll have to read Class::Prototyped, the implementation
sounds interesting.
PPS. You may want to defend C::P over at Class::Classless vs. Class::Prototyped
In reply to Re: Re: When to use prototype inheritence?
by bsb
in thread When to use prototype inheritence?
by bsb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |