comment on

Do what you want with your proposed OO framework, but please acknowledge that it belongs as a competitor with all the others that have come before, some of which are in very widespread use.

Consider whether your fixation on getting your framework adopted into Perl core is based on ego.

Make some software, show it to the community. If it works well, it will be used. What more do you need?

TIMTOWTDI

The way forward always starts with a minimal test.

In reply to Re: The Corinna RFC for getting modern OO into the Perl core is taking shape by 1nickt
in thread The Corinna RFC for getting modern OO into the Perl core is taking shape by Ovid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks