deb wrote: > Hi, > > Here's some (unfinished) code I am trying to use with Getopt::Std, > > #!/usr/local/bin/perl -w > # > use Getopt::Std; > use diagnostics;
Ooops! You started your executable code without use strict; > [snipped--No point in even scanning it without first letting the error-checking of the compiler work.] > > When it's executed, as "test.pl -h" here is what I get in response: > > Name "main::opt_h" used only once: possible typo at test.pl line 16 (#1) > (W once) Typographical errors often show up as unique variable names. > If you had a good reason for having a unique name, then just mention it > again somehow to suppress the message. The our declaration is > provided for this purpose. > > USAGE: test.pl [-h] -n [EMAIL PROTECTED] > > -h This message > -n <[EMAIL PROTECTED]> > > The program is functional, but strict settings complain, right? No, not right. Functional programs do not generate errors under strict. Programs that cannot meet strict compilation function, if at all, only by accident. > So what do I > do? Turn strict back on, and repair the errors cited until strict no longer reports any errors. That's all the help anyone can really give until you trun strict back on. Joseph -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
