I sincerely hope that you change this habit.
Now.
Do you like starting debugging without having a clue which
file you had problems on, or what helpful information was
in $!? How about your co-workers?
For these reasons and more, this is something that I feel
extremely strongly on. I do not like working with code
written by people who did not understand that this matters.
I do not want to depend on people who do not appreciate
this. Not knowing that trying to trap good error messages
is important is one thing, but refusing to learn is a
fireable offence in my books.
(And yes, the strength that I put into that statement
does reflect a few very miserable late nights that
I do not want to repeat. Ever.)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.