I wrote the following test and ran it under version 5.005_03 of perl. It showed that the warning was on the
print line before the
if. Printing undef will result in the warning.
#!/usr/bin/perl -w
use strict;
use Data::Dumper;
use constant index1 => 0;
use constant index2 => 1;
my $rec = [ undef, 1 ];
print Dumper($rec); # inspect before if
print "$rec->[index1] $rec->[index2]\n"; # warnings here (line 11)
if ( defined $rec->[index1] &&
$rec->[index1] ne '' &&
defined $rec->[index1] &&
$rec->[index1] eq '1' )
{
print "OK\n";
} else {
print "Not OK\n";
}
print Dumper($rec); # and check again after if
I don't think your if test
will 'autovivify' anything because of the short circuit behaviour of the && operator. has anything to do with autovivification at all, given that the $rec has a fixed number of records. See
pg's comments above and below.
$VAR1 = [
undef,
1
];
Use of uninitialized value at ./p09.pl line 11.
1
Not OK
$VAR1 = [
undef,
1
];
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.