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
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Cool (Score:1)
Re: (Score:1)
Yes, the most public one is Reaction [0beta.co.uk] which is being built by the guys at Shadow Cat Systems [shadowcatsystems.co.uk] (makers of DBIx::Class and other fine spirits). I have also received a number of emails from a few people who are building MVC style frameworks on top of Moose.
It should be noted that Moose plays fairly well with Catalyst (aside from one small issue with subroutine attributes and the 'extends' keyword which is easily worked around). And a number of people are already using that combination in production. At $work
Link and doc issues (Score:1)
The main Moose page is very light on content, and the next step seems to be the cookbook pages, where I only have a choice of a range of levels of complexity in the demos.
I've found it really hard to find answers to specific single questions.
How do I do simple inheritance?
How do I do a single validating property?
Now frankly, I don't care about th
Re: (Score:1)
First, the cookbook [cpan.org] link has now been fixed, thanks for spotting that.
Second, I freely admit that Moose might not be ergonimically correct for everyone. I based it heavily on Perl 6, but also added in my own twists and a few misc bits I have ripped off from other languages. But, this is Perl so TIMTOWTDI :)
As for your complaint about the docs. Well, I can't argue with you there, the docs are not as comprehensive as they could be (although I think they might have gotten better since you last lo
No $self (Score:1)
But a really nice feature for me would be something (attribute, Moose declaration, source filter (I don't even care)) to say "this is a method" and automatically give me $self (or $class for a class method).
[hmmm... maybe I said this already]
I understand that's not the focus of Moose, but is something like that on the road map? Or is that an invitation for a MooseX something module? (MooseX::Selfless)
Re: (Score:1)
We had a method and self keyword in place for a while, it looked like so:
And self was implemented as a function which was redefiend locally. But to be honest, it added a fairly high amount of overhead to each method call (the wrapper subroutine and the local redefining of self), and it polluted the stack traces really badly with lots of ANONs. In the end I removed it cause it was just not the right way to go about it.
As for future plans to supp