Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
The name is mostly a way of identifying who is "in the know" and not. People who use "Perl" and "perl" correctly can be identified as having some basic level of community knowledge.

Well that's all well & good if you subscribe to an elitist philosophy. I see it more as a ritualistic hazing that perpetuates in the monastery. It's a joke that never gets old, like when you go skiing & people on the chairlift clack their skis together to drop snow on the heads of people below them. I've fallen victem to this one myself; And that was after years of professionally developing Perl applications. It begs the question, if a 'back-ronym' is widely known & accepted, then does it replace the original word? And if so, does that make writing "PERL" ok? The generally accepted response is "no".

But the reality is that this is one of those pieces of misinformation that have gotten propagated early on in Perl's history, made it's way into poorly researched FAQ's & books, and has been passed on as folklore. As such it has become one of the most repeated criticisms in the history of the site. And while in frequency it wouldn't hold a candle to "use strict" neither does it hold nearly as much merit.

Wait! This isn't a Parachute, this is a Backpack!

In reply to Re^4: Taking advantage of multi-processor architecture by gregor42
in thread Taking advantage of multi-processor architecture by bedanta

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (2)
As of 2022-08-13 09:57 GMT
Find Nodes?
    Voting Booth?

    No recent polls found