in reply to Re: Errors with sorting hashs
in thread Errors with sorting hashs
I'm getting the following when I do that.
Use of uninitialized value in numeric comparison (<=>) at
./source_virus_count.pl line 70 (#1)
(W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl tells you what operation you used the undefined value in. Note, however, that perl optimizes your program and the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program.
Uncaught exception from user code:
Use of uninitialized value in numeric comparison (<=>) at ./source_virus_count.pl line 70.
main::hashValueDescendingVirus called at ./source_virus_count.pl line 99
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Errors with sorting hashs
by dragonchild (Archbishop) on Aug 27, 2004 at 14:15 UTC | |
by red-beard (Scribe) on Aug 27, 2004 at 18:17 UTC | |
|
Re^3: Errors with sorting hashs
by red-beard (Scribe) on Aug 27, 2004 at 14:23 UTC | |
by red-beard (Scribe) on Aug 27, 2004 at 14:31 UTC |