On Sat, 21 Apr 2001 13:40:29 PDT, Vicki Brown wrote: :Let's imagine for a moment that you have a Perl script, fooscript. It starts :like this, with a POD header all ready for pod2man. : : : #!/usr/bin/perl : : =head 1 NAME : : fooscript - a script that really foos : : =head SYNOPSIS : : fooscript -f -g -h : : :Now, consider foa moment that you've made a small editing mistake. There is a :blank line above the : : #!/usr/bin/perl : :Now, imagine that you run this script... : : fooscript : :What will your system administrator's reaction be? Eye-popping, hear-tearing rage? Been there! Done that! Of course you don't need POD for this. When I was new on the job, one of my users had a nice plain-ASCII data file named "AAA" in his home directory. AAA looked like this: * * * * * AAA * * * * * 1 0 0 1 0 1 1 1 0 1 1 0 0 0 0 1 ... Of course, the user wasn't quite sure what Unix file permissions meant, so just to be sure he'd have as much access as he might need, he did chmod u+rwx AAA Everything worked perfectly until one day he typed * The rest of the story is left as an exercise for the novice sysadmin/detective. Michael P.S.: This is another good reason not to have '.' in one's PATH. ==== Want to unsubscribe from Fun With Perl? Well, if you insist... ==== Send email to <fwp-request@technofile.org> with message _body_ ==== unsubscribe