comment on

It works for me:

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

my @arr2 = qw( mcs scr tsz unh );
my @arr1 = qw( spec.srn.1234 sepc.mcs.1234 );

for my $strfile (@arr1) {
    my @arr3 = split(/[.\n]/, $strfile);
    if (grep (/^$arr3[1]$/, @arr2)) {
        print "Entered in IF Loop\n";
    } else {
        print "Entered in ELSE Loop\n";
    }
}

__END__

Output:
Entered in ELSE Loop
Entered in IF Loop
[download]

Are you sure your input contains what you think? Try adding the information to the output:

    if (grep (/^$arr3[1]$/, @arr2)) {
        print "Entered in IF Loop: /^$arr3[1]\$/ found in (@arr2)\n";
    } else {
        print "Entered in ELSE Loop: /^$arr3[1]\$/ not found in (@arr2
+)\n";
    }
[download]

Also note that I used $arr3[1] instead of @arr3[1]. warnings told me to do so.

لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

In reply to Re: perl grep with regex by choroba
in thread perl grep with regex by swissknife

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.


P is for Practical
	PerlMonks