> > How can you trust *any* of the code they produce?!?!
>
> Because perl is for the lazy. I want an easy way to arrange for all my
> programs to run under strict/warnings, should that be my inclination.
Well, I think this reasoning has a flaw in it. First, if they're too
lazy to type two lines, they're *definitely* too lazy to pay attention
enough to get all the my()'s right (let alone the underlying logic of
the program!).
Plus, this is easily fixable by a site policy. I wrote a script called
"newperl" that creates a blank file with all the correct stuff at the
top. I run it anytime I start a new Perl script. It took me about 5
minutes to write. Writing a script like this is simple, then you need a
formal policy:
1. When writing a new Perl program, type "newperl"
2. Edit away
3. Don't forget to use RCS!
There is a "cstyle" program for styling C programs. Maybe someone needs
to write a "pstyle"? Then, this could check for the appropriate
directives, saying:
nwiger@host$ pstyle myscript
pstyle: error: "myscript" missing "use strict" pragma
pstyle: error: "myscript" missing "use warnings" pragma
> Can't we make everyone happy by making it a build-time option?
I really don't think this is a good idea. We should decide one way or
the other, and have Perl be Perl. Having scripts that run one place not
run another is not my idea of "fun". And Perl should be fun.
-Nate
