Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-14 Thread Owen
On Sat, 13 Dec 2003 18:12:17 +0100 Jerry Rocteur <[EMAIL PROTECTED]> wrote: > I'm trying to be a good boy and use strict and warnings .. > > The more I do, the more I feel I'm wasting so much time and should > become productive, my code looks full of 'my' Because so many people in c.l.p.m said

RE: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-14 Thread Bakken, Luke
> uninitialized value in > pattern match (m//) at ./getopt.pl line 14.' Use the standard Getopt::Std module to process options. Don't do it yourself. > Line 14 is the while line.. > > I've tried all sorts of stuff with defined but keep getting syntax > errors. I've tried perldoc warnings and

Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-14 Thread Jerry Rocteur
ttle routing gives me 'Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.' Line 14 is the while line.. I've tried all sorts of stuff with defined but keep getting syntax errors. I've tried perldoc warnings and perldoc perllexwarn .. In any case, unl

Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-14 Thread Jerry Rocteur
lies. My DBI Perl is even more of a headache ;-(( Anyway, enough whining, now I've going through code that is working and thought I'd see the big difference if I change it to use warnings and strict and this little routing gives me 'Use of uninitialized value in pattern match (

Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-13 Thread drieux
On Dec 13, 2003, at 10:01 AM, Wiggins d'Anconia wrote: [.. A decent template, any gurus have improvements? [..] my stock gag, looks like: my $opt = parse_cmd_line_options(); ... #--- # These are the Subs for the parse_cmd_line_options. #

Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-13 Thread R. Joseph Newton
Wiggins d'Anconia wrote: > More code showing specifically why I have been rambling about $_ in the > last couple of days. If you are going to shift off the argument list > why not just do it in the while loop when you are setting $_? Thanks, Wiggins, and keep on rambling. The point needs reiter

Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-13 Thread Rob Dixon
ing and > thought I'd see the big difference if I change it to use warnings and > strict and this little routing gives me 'Use of uninitialized value in > pattern match (m//) at ./getopt.pl line 14.' > > Line 14 is the while line.. 'use warnings' will moan at

Re: Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-13 Thread Wiggins d'Anconia
er coding in Perl for 3+ years... Anyway, enough whining, now I've going through code that is working and thought I'd see the big difference if I change it to use warnings and strict and this little routing gives me 'Use of uninitialized value in pattern match (m//) at ./getopt

Use of uninitialized value in pattern match (m//) at ./getopt.pl line 14.

2003-12-13 Thread Jerry Rocteur
lies. My DBI Perl is even more of a headache ;-(( Anyway, enough whining, now I've going through code that is working and thought I'd see the big difference if I change it to use warnings and strict and this little routing gives me 'Use of uninitialized value in pattern match (