But merlyn has made it clear that any standard Moose CGIP will not be in the CGIP distro
If you keep misquoting me, I shall be compelled to keep correcting you. If you want the last word, stop misquoting me.

There's nothing "non-standard" about a Moose implementation that supports prototype style inheritance. I had a lengthy discussion yesterday on the irc.perl.org #moose channel about this very topic, and concluded that with a small amount of programming, you can get t/200_examples/006_example_Protomoose.t in the Moose distro into a trait rather than a base class, and it would support prototype-style inheritance and be compatible with nearly all of the rest of Moose.

So, please, stop your whining. You can use standard Moose, and add prototypes, and create a Moose-based CGIP.

Stop saying I'm making it impossible. I've just said I've done the footwork to prove it's possible. Now it's up to you to either comply, go your own way, or continue to look foolish.

-- Randal L. Schwartz, Perl hacker

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

In reply to Re^3: a Moose CGIP shall not receive merlyn's blessing by merlyn
in thread CGI::Prototype leverages objects for web app control by metaperl

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.