> ----- Original Message -----
> From: "Jeff Pinyan" <[EMAIL PROTECTED]>
> To: "Aaron Craig" <[EMAIL PROTECTED]>
> > Before I answer your question, I have to ask you to not use
> > subroutine prototypes. 9 out of 10 Perl programmers use them
> > incorrectly or don't know what they do.
> >
> > The problem is: PROTOTYPES MUST BE SEEN BEFORE THE FUNCTION IS
> > CALLED. So few people realize that (for one reason or another[1]).
For that reason, I usually do my function definitions at the top of my
programs. That way they've already been thoroughly parsed before ever
being called. I used to do that in my C code, too.
One problem there, though, is that you have to look for where the
actual program begins. Good documentation helps, but that sort of
structure can hinder human-readability.....
=====
print "Just another Perl Hacker\n"; # edited for readability =o)
=============================================================
Real friends are those whom, when you inconvenience them, are bothered less by it than
you are. -- me. =o)
=============================================================
"There are trivial truths and there are great Truths.
The opposite of a trival truth is obviously false.
The opposite of a great Truth is also true." -- Neils Bohr
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
