I tend to disclaim whether the code is known to be good or
not. I've only posted small tidbits, and usually from a
working program, in order to get around to my problem (like
Referents Anonymous.) where I will write what I'm attempting to do.
But I tend not to write code in the majority of my posts,
instead relying on the fact that theory translates better
than code for problems we may all be facing at some point.
As for the braces problem, for verbs, the braces start on
the line below, but subs keep the braces on the same row. It's
actually got a method to the madness. In the case of a verb,
the code may get executed, and thusly, I don't want to be led
into the code by my eyes while I'm reading over it. In the
case of a sub (although it has a verb name), once I get to a
sub, it will be executed, and so I do want my eyes led into
the code. It's a case of "I might" vs. "I will".
ALL HAIL BRAK!!!
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.