You wrote:

In practical perl, multiple inheritance is used, composition is used, delegation is used, roles are used. None of these concepts or their usages are going away.

The Corinna MVP is designed to support composition, delegation, and roles. It almost sounds like you're suggesting we're taking this away, but we're not, so I must be misunderstanding what you're saying. And if you absolutely need multiple inheritance, we have a special syntax for this very edge case.

Corinna's not taking anything away. It's simply that the MVP is designed to be cautious by nature rather than risk all the missteps Perl has had with given/when, smartmatch, pseudohashes, indirect object syntax, the SUPER bug, and so on. I'm not saying we haven't made mistakes, but rather than shove too many things into Corinna precipitously, we need to understand how the MVP will play out.

After we work out the kinks in the MVP (and we will have them), if you want native MI support in Corinna, lobby for it and start and RFC. You don't even have to implement it yourself. Win enough people to your position and convince someone on P5P to sponsor the work.


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

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.