First, I think that anything that adds to a given feature in Perl, whether I use it or not, is a good thing. I like your ideas and would love to see the discussion go further. That said, I have a pretty good idea of why p5p might be ... reluctant to do more with lvalue subs.

I maintain a webapp that's half in Perl, half in Javascript. It's almost 8 years old and there have been at least 15 different people who've worked on it, then walked away. There are no more features for this thing - just bug fixes. And, each bugfix, no matter how trivial, takes at least a week from start to finish. I just wrote up a proposal to fix a bug that affects one aspect of one feature when it's used with another feature. This fix will take at least 3 months and involve testing the entire application. Reason - the bug is in a function that every feature in the application uses.

Perl is kinda like that. It's not a clean, well-factored application. The guts are a mess of C macros, typedefs, crazy optimizations, and OS-specific code. When you start messing with something as integral as subroutines, you never have enough regression tests. You're talking about affecting a core subsystem that, probably, many other subsystems depend on in some way or another. And, it may not be clear what depends on it. I've fixed bugs in section A that exposed hidden dependencies in section G.

However, despite all that, I think the discussion is definitely a good one. Without a lance, you cannot tilt at windmills.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

In reply to Re: Experimenting with Lvalue Subs by dragonchild
in thread Experimenting with Lvalue Subs by Limbic~Region

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.