For Programmers: Free Programming Magazines  


Home > Archive > PERL Beginners > March 2005 > A strange solution to warnings about uninitialized variables









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author A strange solution to warnings about uninitialized variables
Walter A Poor Jr

2005-03-30, 3:56 pm

This is my third note on this subject, and I hope no-one objects.

My questions (and those of other members) were why perl sometimes claims
some variables have not been initialized, even when direct investigation
proves that the variables in fact have valid real values. Several people
suggested helpful ideas, but none of them worked.

But then my PC tech installed a program to find and locate spyware on my
PCs. The problem with Perl's strange warnings went away instantly, and
have never returned. Nothing else changed: same input files, same
program, and same version of Perl.

Does this make sense to anyone? Would anyone have predicted this
behavior?

Thanks,
Walt
Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com