Conway argues that leaving off the parens from user-defined subroutines makes them harder to distinguish from built-ins.

That might, just, possibly be the case for those very few heroic martyrs who insist on doing everything in green&white and eschewing the benefits of syntax highlighting.

But they are a rare breed indeed. For the rest of us, depending upon our needs and taste, built-ins can be made to stand out--or not--as we so chose.

Were this a truly important distinction for me (or anyone using my editor) to make, then I could have built-ins appear double-bold fluorescent pink letters on a day-glo yellow background. I might even be able to make them flash, though I'm not sure because I've never thought to try.

But I don't, and I doubt you'll find many who would. My argument with this particular piece of "best practice" is not that the argument is wrong, but that it is the wrong argument. Why is it important to make that distinction?

User functions are just as important as built-ins; but no more so. Besides which, most built-ins can be overridden by loaded modules, and many are to good effect. What benefit this distinction then?

Given the effects that book has had, I'm kinda surprised that anyone is still promoting it.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^2: [beginner is learning] How comes before I ask a question here, it is answered by BrowserUk
in thread [beginner is learning] How comes before I ask a question here, it is answered by aquaplanet

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.