Bâââh! acronyms

I prefer not to use them. It's bad grammar, it's unclear and it's lazy.
Besides that, most acronym-users seem to think that they have the only possible explanation for an acronym. Try to explain to the union of pot-smokers that you want the uninterruptable powersupply sent via universal parcel service.
The 'YAML' kind of acronym you refer to is the worst... even if you unpack it it's still not clear what it actually means. Those always give me a symlink-to-parentdir feeling. ;)

if( exists $aeons{strange} ){ die $death unless ( $death%2 ) }

In reply to Re: Acronym assumptions. by Ojosh!ro
in thread Acronym assumptions. by Trizor

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.