in reply to
Re^2: a Moose CGIP shall not receive merlyn's blessing
in thread CGI::Prototype leverages objects for web app control
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.