No Moose breaks intentionally in the course of development. I'd say the API is the same but I've personally had very minor, but existent problems with it too. And this is a reality of any software release, if you think otherwise you just have your head lodged in your arse. I'm not bitching, I love Moose -- and personally I like the design decisions that *can* break older code.
  1. isa => "foo|bar" (used to work), now requires isa => "foo | bar"
  2. the internals of MOP used to dictate ->clearer undefs a slot, when it now deletes it, predicate likewise use to check for defined(), it now it checks for exists()
  3. __PACKAGE__->meta->make_immutable vs __PACAKGE__->make_immutable

Now #2 wouldn't or shouldn't have destroyed anything if the user had used predicate/clearer, but how many people mistakingly check the return on the attribute? ie if defined $foo->bar?? To make matters even worse, neither ->predicate nor ->clearer is documented in the Moose documentation, it was instead in the underlying framework Class::MOP, which changed. Moose was just built atop the foundation of MOP. (You can find my Moose documentation in the wikibook)
Point here is that software develops, and if you know what is being made "better" well enough you can often tell the nominal "what-if"s that you're neglecting.


Evan Carroll
www.EvanCarroll.com

In reply to Re^4: Trying to make perl suck less again by EvanCarroll
in thread Trying to make perl suck less again by EvanCarroll

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.