Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I've posted a bunch of my scripts on http://www.webdragon.net/perl.htm that I've released to the public, if you'd care to have a look at them and some of the ugly hacks required to work around the way the world works :-D

    I'd add to your list
      o write really good documentation (in perl .pod format, preferably) as you go
      o document your changes with a decent changelog (and comments within the code) as you repair your programs over time.
      o the reason for this is: maintainability.
      o write tests (good ones) to prove your code works the way it's supposed to. beat the hell outta it with tests. It'll still break on someone else's system, but not quite as often ;)