[Catalyst-dev] Moose + Catalyst port

[Dave Rolsky]

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_.


-dave

/*==========================
VegGuide.Org
Your guide to all that's veg
==========================*/