[Catalyst-dev] Moose + Catalyst port

[Christopher H. Laco]

Dave Rolsky wrote:
> On Sat, 15 Mar 2008, Guillermo Roditi wrote:
> =

>>> > COMPONENT calls $self->NEXT::COMPONENT. why? We have no superclasses.
>>> > I figure this is a MI thing. Are we sticking with NEXT for the Moose
>>> > port? I was thinking of moving to just using method modifiers. I have
>>> > no clue what to replace this call with. I could use some help here.
>>> > COMPONENT, in the case of not being able to build a new instance via
>>> > new just blesses the config + args. Uhm. do we need to keep compat for
>>> > this? The Moose port will always return an object on new because
>>> > Moose::Object will do that for us.
>>>
>>>  One thing you'll need to do is look for uses of this sort of stuff in
>>>  plugins, which is what COMPONENT is used for, AFAICT. Same goes for
>>>  ACCEPT_CONTEXT.
>>
>> After 6 hours of hacking on this I am still so fucking lost. i guess i
>> just do not grok NEXT or something. I just can't explain to myself why
>> a class with no superclasses would ever call NEXT.
> =

> I think it does this because it may have _subclasses_.

Or, think of it another way. Instead of subclasses...aka stacking =

classes on top of each other... think composition...stacking classes =

beside each other in another class. Like plugins that don't sublasses =

anything, but get stuffed into something else. And NEXT just allows them =

to pass traffic along to the next guy, without knowing who the next guy =

really is.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://lists.scsys.co.uk/pipermail/catalyst-dev/attachments/20080315/=
09932756/signature.pgp