The initial question I came on here to ask was for someone to show me the usefulness of the current precedence -- how are they relying on it or using it in any production or cpan code.

I'm not trying to convince anyone of anything -- as I can't say "we should do this", unless no one can come up code where the current precedence is used/useful/required -OR- how a change in precedence as I have outlined would cause a problem.

Parens are a sign of either a complex statement OR insufficient strength in the grammar. Did you check out the pdf I pointed to (the references he quotes in the pdf point back to HERE on perlmonks..). Oddly enough, he quotes perlmonks in discussing good Domain Specific language design, but only has examples in python, scala, ruby and smalltalk. Here is someone who was familiar enough with perl that he could quote erudite discussions on perlmonks, yet didn't use in any of his examples.

Qualities of good languages are generalization : reduce concepts by replacing a group of more specific cases with a common case.

Compression -- Provide a consise language that is sufficiently verbose for the domain experts. -- Specifically the goal being to "reduce the amount of expressions or to simplify their appearance while the semantics are not changed" ...et al...

The point here being to simplify the language in a way that loses none of its semantics, but simplifying the expressions.

So far no one has offered any examples of how this change would cause problems. It's not like I'm new to perl -- I've been using it since the early 90's when P-III was just being replaced by P-IV. It took me forever to change out of the P4 style and move toward P5... I'm not someone who is highly open to change. But neither am I for killing a language for the sake of preserving for as a future archival language.

In reply to Re^6: Precedence design question...'x' & arith by perl-diddler
in thread Precedence design question...'x' & arith by perl-diddler

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.