My tip: Learn to solve your own problems
Before I consider posting to Perlmonks (or bothering co-workers ;) ) I always try to write a smaller program that illustrates my problem. I give it the data (hardcoded where possible) that I expect to get (or to compare with the data I expect from my code) and work from there.
This allows me:
- Controlled space where I can experiment
- Clean brain space to concentrate on the problem
- Knowledge that I can't break anything
- I can have finer control over running the test area
I say try it (if you don't already).
Just my 2p
SP
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.
|
|
