comment on

Please don't misuse the code tags.

Use <p> tags in front of your text paragraphs, and keep the code tags for the real code sections. Thanks.

Your line 123 is reached and executed whether $gSDDdata[$sdd]{source} and/or $gSRSData[$srs]{sect} are defined or not.

Is that really what you want?

Maybe you want to take some action where you print your "m" and "n" (e.g. continue with the next loop)?

update: example added:

#!/usr/bin/perl
use strict;
use warnings;

my @out = ( 1, undef, 3 );
my @in  = ( 4, 5, undef );

OUTER: 
for my $o ( @out ) {
  INNER: 
  for my $i ( @in ) {
    if ( !defined $o ) {
      next OUTER;
    }
    
    if ( !defined $i ) {
      next INNER;
    }

    printf "\$o(%d) * \$i(%d) = %d\n", $o, $i, $o * $i;
  }
}
[download]

update2: modified code;

In reply to Re: Use of unintialized value in pattern match (m//) at x.pl line 123 by linuxer
in thread Use of unintialized value in pattern match (m//) at x.pl line 123 by gibsonca

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks