Re: Moose speed and schedule

# from Stevan Little
# on Saturday 11 November 2006 08:11 pm:

>A question though, is this benchmark including Class::MOP/Moose   
>compile time?

I would be curious to see the benchmark code.

# from Jonathan Swartz
# on Saturday 11 November 2006 06:34 pm:

>In the meantime, does anyone have a recommendation for an alternate  
>class framework I can use that will make the eventual jump to Moose  
>as painless as possible?

Disclaimer:  It's nowhere near a "class framework", but makes object 
accessors much less painful.

I did Class::Accessor::Classy just recently because I don't quite need 
an object framework (well, for some non-fatal value of "need") in this 
project yet but was really starting to get sick of the Class::Accessor 
stuff.  I'm hoping it will be a somewhat painless transition to Moose 
compared to the sort of thing that Class::Accessor forces on you WRT 
overriding get()/set(), multiple inheritance headaches, no 
SUPER::set_foo(), new({}) constructor, etc.

--Eric
-- 
I arise in the morning torn between a desire to improve the world and a
desire to enjoy the world. This makes it hard to plan the day.
--E.B. White
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------