Well, there's already ample precedent for "ugly names like that", such as __DATA__ and __PACKAGE__. Programmers need all the help they can get at the time of devising useful typographic conventions for identifiers, since the good alternatives are so few. One of these few good alternatives is the all-cap identifier, and I think it is a shame that the core has declared it off-limits.

Update: Besides, the core can still reserve specific all-cap identifiers such as the one you list, just like it reserves any other specific keyword (if, else, for, etc.). My objection is to the blanket claim on all all-cap identifiers.

the lowliest monk

In reply to Re^3: All uppercase subs by tlm
in thread All uppercase subs by blazar

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.