[Catalyst] reserved word?

[Alan Humphrey]

Yes, I want to be careful, but careful of every method that might be
loaded now and in the future by Catalyst and Plugins?  Seems like a
fragile situation.

I'm willing to live by the rule that says only use the predefined
actions in the application class, but then I look at mojomojo and see
that it uses additional subroutines, so the rule doesn't seem all that
hard and fast.  Is it acceptable for mojomojo to break when someone
decides to add a method called "static" to a plugin?

By the way, the docs are silent on this "rule".  It would be very
helpful if the Into talked about and if the Tutorial stepped through the
process of creating a controller and extending the app there.  The
tutorial currently implies that you are free to add whatever you want to
the application class.

- Alan

-----Original Message-----
From: catalyst-bounces at lists.rawmode.org
[mailto:catalyst-bounces at lists.rawmode.org] On Behalf Of Sebastian
Riedel
Sent: Tuesday, April 19, 2005 12:13 AM
To: Catalyst List''
Subject: Re: [Catalyst] reserved word?


Am 19.04.2005 um 03:14 schrieb Alan Humphrey:
> Are there other "reserved words" we should worry about?

Like i said before, you better not blindly define methods in the 
application class, use Controllers. ;)

Your application class inherits all methods from Catalyst, 
Catalyst::Dispatcher, Catalyst::Engine and Catalyst::Engine::*.
And naturally every plugin you loaded.

So the list is quite big and you better be careful about other actions 
than (begin, auto, default and end).

--
sebastian


_______________________________________________
Catalyst mailing list
Catalyst at lists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst