The Perl Debugger (perl -d
) is your friend. The 'm' command reports on the various methods available to an object; use it just after you have instantiated the beast --
my $obj = Class::new();
DB<1> m $obj
'T' gives stack trace information and tells the context the routines are called in.
I also use 's' step into method calls and then explore with 'w' and friends to see where I really ended up.
In terms of graphics, I have yet to find something that beats pencil and paper for the fine detail, white-board and Visio diagrams for the over-all structure.
And Document Everything! Build POD, ReadMeFirst files, Twiki pages, what ever make you comfortable. Even if you don't have to come this way again, someone else will.
I Go Back to Sleep, Now.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||