All the Perl that's Practical to Extract and Report
use Perl Log In
chaoticset (2105)
(email not shown publicly)
http://chaoticset.perlmonk.org/
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)
JAPH. (That's right -- I'm not Really Inexperienced any more.)
I'm not just here, I'm here [perlmonks.org], and here [javajunkies.org] too, I ramble randomly in my philosophical blog [blogspot.com] and my other blog [blogspot.com]. Soon I'll come in a convenient six-pack.
Journal of chaoticset (2105)
0 For 0
And maybe if I really try I can poop diamonds, too...but I doubt it.
Anyway, it doesn't matter. The teacher that was taking the CGI class with me sent me her scripts, and she's looking to fix the file upload. I have a guess of why it's not working, and fired off an email, but should probably look all the code over anyway, just for practice's sake -- maintaining code is likely something I'll end up doing at some point. Might as well start early.
One thing that struck me is the great length taken with her project to break it into multiple files. Newser was one script. 600 lines, sure, and two CSS and a template file and a database, but that's it.
Of course, Newser was a lot simpler, too.
Doesn't matter. I'm sure I'll have some interesting observations up reading the code.
--Larry Wall in stab.c from the perl source code
maintaining code (Score:1)
Much of the code will be written badly or at least in such a way as to really annoy you. Worse still you will probably have to debug programs in unfamiliar and lesser languages like Java or VB.
Hacking other peoples code is unpleasent at the best of times. If you are lucky then there is some documentation or some kind of guidelines on how things are done but usually there is neither.
One of the nice things about
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;