I ++'d this thread. Even though I don't make a practice of using non-meaningful names, I think it's hilarious to stumble across something like this when I'm supporting/maintaining code. The only reason I refrain is because my memory blows chunks. I need meaning ful names so, when I'm revisiting my code at a later date, my intentions are fairly apparent.

This thread does bring to mind a funny, but extremely off-topic, error message my team received from an OS core dump on an older VMS system some years ago. The error message was "Shut 'er down Clancy, she's pumping mud!" Oddly, this error message was undocumented. After a fairly lengthy conversation with one of the OS's authors, he stated that this error message should never be reached. For some reason, they had a conditional similar to the following:

if true {
   ...do something;
} elsif false {
   ...do something else;
} else {
   print "Shut 'er down.....";
}
[download]

And somehow, we managed to be neither true nor false.

If things get any worse, I'll have to ask you to stop helping me.

---

---

• 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 How to display code and escape characters are good places to start.