dragonchild,
We have Tutorials for many things that are already explained in the documentation from using pack/unpack to command line arguments. The point is that not all people immediately understand this information and they need it presented to them in a different way. Perhaps I am thinking more of a beginner's guide to precedence. It seems that for a lot of people who's first language is Perl - they come to expect the Do What I Mean (DWIM) approach. I often get WTF comments in #perl when I am explaining an answer by stating that "...binds more tightly than...".
Or perhaps - I am just misjudging the need.
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, 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, 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.
|
|