NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: What OO paradigm? (Score:1)
DISCLAIMER: I am biased [cpan.org], and all my "facts" come secondhand from people who have switched to Moose, so take it with a big giant grain of salt.
I have been seeing some blowback with Inside-Out objects, mostly centered around the difficulties with dumping them and the need for them to be DESTROY-ed to properly manage them. Most of the helper modules tend to try and fix these issues, but in doing so, they tend to break t
Re: (Score:1)
As the author of Class::InsideOut, I would say that people should only use inside-out objects if they have a particular need for doing so and understand the implications. No one should use inside-out objects "just because" or because they think it's a best practice.
I still refer people to my YAPC talk [dagolden.com] as a good articulation of the issues.
I've only recently had the opportunity to work with Moose and I'm very impressed with it -- though I found a bit of a steep learning curve trying to understand type co
Re: What OO paradigm? (Score:1)
The most magical bit is Sub::Name, followed by some of the XS we have in Class::MOP now (only about 20-30 lines of XS in total too). And recently some of the BestPracticalistas have been looking to make a Pure Perl alternative to that as well. In general we do our very best to keep core Moose as clean and easy to install as possible, and all the crazier stuff (see also MooseX::Compile) is in a different distro.
- Stevan
Reply to This
Parent