Currently, all of the logic for checking/storing cached anonymous
classes lives within Moose::Meta::Class->create_anon_class. And the
cache is just a package scoped hash declared just outside the method.

I'd like to break that up a bit and define a couple of methods
specifically for dealing with the caching of anonymous classes. What
that buys us is for people wanting to override the create_anon_class
behavior (eg.
http://github.com/nperez/moosex-anonclassname-uuid/tree/master ) we
don't need to duplicate the caching code. 

Thoughts?

-- 

Nicholas Perez
XMPP/Email: n...@nickandperla.net
http://search.cpan.org/~nperez/
http://github.com/nperez

Reply via email to