Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I've tried to use Moose three times now for Real Work (albeit small scale work) and failed. Not because the state of the code, but because of the state of the docs.

    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 the answers to those specific things, but it's annoying when I can make a simple two-property class ( ->hello and ->world ) but making it incrementally more complex is hard, because the next level of demo class implements 50% of all the features in the toolkit and confuses things, and the third demo is already up into advanced material.

    I'd like to see a series of simple examples. Hello World + Inheritance, Hello World + Validation, Hello World + etc...

    Also, the Module::Cookbook link doesn't work.
    • Alias,

      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