I have spoken out against such changes in the past (Re: Thoughts on replacing -> with .) because I think that the benefits are overestimated relative to the costs.

Here, only the wizards will be sure they know what they are doing, when they omit the parentheses. And the wizards will know that the x-operator has higher precedence. Changing Perl to the more intuitive way (I admit it would be) will break older code and will be very difficult to spot.

I also think that less parentheses is not automatically cleaner code. Especially, when you have to remember rarely used and recently changed precedence rules.

And lastly, your initial post has already more than 3000 characters, not counting your follow ups, which makes more than 1500 pairs of parentheses you could have typed in your code... ;)

In reply to Re: Precedence design question...'x' & arith by hdb
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.