[Catalyst-dev] Why is APP not instantiated?

Guillermo Roditi groditi at gmail.com
Tue May 20 17:05:43 BST 2008


All components which can->(COMPONENT) are treated as instances by
catalyst at setup component time. MyApp ISA Catalyst which ISA
Component and in some cases also isa Controller which ISA component as
well. MyApp however gets fancy special treatment and is not
instantiated.

instantiating it does not break the test suite
if we can guarantee that $self will be an instance in
Controller::action_namespace that would make my life a lot easier, it
would also likely buy us some startup and runtime gains as well as
eliminate a decent chunk of code

I am going to make this change, if you have good reason to believe
this is a Bad Idea then please tell me so, via email to this list
outlining why exactly this is not good along with a broken _usage_
case. Complaints without proof of breakage will be ignored. The Moose
port has been having problems because people are quick to voice their
opinions without really really thinking about things and it's created
a bit of extra work for me and konobi.


-- 
Guillermo Roditi (groditi)



More information about the Catalyst-dev mailing list