Why not use Attribute::Protected to define private etc. methods
Using
my $my_method = sub {}
doesn;t that have a drawback if you want to use it before it's been defined?
Haven't tried it so might be wrong on that.
Matt S Trout <[EMAIL PROTECTED]> wrote: On Wed, May 09, 2007 at 09:02:00PM
-0500, Dave Rolsky wrote:
> This is as opposed to the historical Catalyst plugin pattern of "jam a
> gazillion methods into Context" ;)
Sometimes I wonder if that one is actually a conspirancy by the local
breweries.
--
Matt S Trout Need help with your Catalyst or DBIx::Class project?
Technical Director Want a managed development or deployment platform?
Shadowcat Systems Ltd. Contact mst (at) shadowcatsystems.co.uk for a quote
http://chainsawblues.vox.com/ http://www.shadowcatsystems.co.uk/
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
---------------------------------
Inbox full of unwanted email? Get leading protection and 1GB storage with All
New Yahoo! Mail._______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
