On Thursday 07 June 2001 17:17, Peter Cline wrote:
> >1) warnings do not prohibit the execution. they are just warnings, not
> > errors.
>
> This one seems to.
>
> >2) variables are initialized, but some of them are initialized from the
> >parameters. So, if you pass undefined value as a parameter, the variable
> > can contain undefined value. That's what perl complains about - you're
> > then using the undefined value in wrong context.
>
> The value is defined and passed as follows
>
> my $configFile = "lib/request.conf";
> my %conf = ();
> my $varValueSep = '==';
> my $confComment = '#';
>
> processConfFile (\$configFile, \%conf, \$varValueSep, \$confComment);
>
That's really strange. Maybe you could print $input before the line, and then
print $var and $value? It could generate one more warning and you could see
what's the problematic variable.
--
Ondrej Par
Internet Securities
Software Engineer
e-mail: [EMAIL PROTECTED]
Phone: +420 2 222 543 45 ext. 112
