My experience with PDL is that it is a great way to
produce code, but not to maintain it. Also I find in
Perl that it works better to, instead of turning the
pseudo-code into comments, turn it into function names.
or Perl.
I agree with you that things are changed somewhat because
Perl is already a high level language, so the gap
between what you are trying to do and how you do it is
narrower than it might otherwise be.
Should you wish to go the other way and make PDL into
comments, you will wind up with densely commented code.
While you had a good experience with updating it
(largely because you chose to also update the comments)
it doesn't age so well. This time around you likely
left some comment in there which does not quite match
the code. Or if someone else edits it they will. Add a
few rounds of that and the comments will inevitably
drift out of sync...
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.