It's a good habit to get into. Spots many common errors and points them out to you, when you try to run the script. Even finds them before you try to run the script, if you use the "-c" option from the commandline. For example:
perl -c myscript.pl
For even more information about possible trouble spots in your program, add this line, too (up towards the top somewhere):
use warnings;
While you're learning, you'll get more verbose (explanatory) er
First tip (Score:1)
(type "perldoc perlop" and search for "Quote-like" to read more)
I guess those small things is what makes people say Perl code is unreadable. No, wait!?! That doesn't seem right...
Welcome to the community! (Score:1)
use strict;It's a good habit to get into. Spots many common errors and points them out to you, when you try to run the script. Even finds them before you try to run the script, if you use the "-c" option from the commandline. For example:
perl -c myscript.plFor even more information about possible trouble spots in your program, add this line, too (up towards the top somewhere):
use warnings;While you're learning, you'll get more verbose (explanatory) er