Trouble using LIB.PM to modify @INC

[Mark]

Hello.

My web site recently began spitting out a stream of errors to the error log:

[Thu Jan 19 19:10:40 2006] gen_page.pm: Use of uninitialized value in hash
element at /usr/lib/perl/5.8/lib.pm line 59.
[Thu Jan 19 19:10:40 2006] jpg.pm: Use of uninitialized value in hash
element at /usr/lib/perl/5.8/lib.pm line 59.

For some reason, the LIB module is unhappy with me. It breaks on the
following line:

@INC = grep { ++$names{$_} == 1 } @INC;

I have tried several variations of the statement that passes my private
module path to the LIB module:

use lib "/home/username/sitename.com/cgi-bin";
use lib q(/home/username/sitename.com/cgi-bin);
use lib qq(/home/username/sitename.com/cgi-bin);

All result in the same error.

Any suggestions?

Thanks
-Mark

 

[Mark]

I think I have solved it. The cause looks totally unrelated,
but weirdness does tend to propogate and change form
in Perl. That's why I love it so.

-Mark

 

[usenet]

@INC = grep { ++$names{$_} == 1 } @INC;

FWIW, You might be interested in
perldoc -q include
"How do I add a directory to my include path (@INC) at runtime?"

 

[Paul Lalli]

FWIW, You might be interested in
perldoc -q include
"How do I add a directory to my include path (@INC) at runtime?"

Why would the OP be interested in that? The OP is already using lib.
He said that the lib module itself was giving warnings, and posting the
line from lib.pm that the warnings referred to.

What exactly are you attempting to suggest?

Paul Lalli

 

[Mark]

Why would the OP be interested in that? The OP is already using lib.

What this OP eventually discovered was that his input file was not in
the specified format, and this caused a whole series of weird errors
to propogate throughout the various libraries that were being used.