my %list_of_keys = qw(DNI 1 SNI 1 JRN 1);
my $filename = 'foo,JRN,SNI,bar';

my $regex = join('|', map { "\Q$_\E" } keys(%list_of_keys));

$regex = qr{\b($regex)\b}; # case insensitive?

while($filename =~ /$regex/ig) {
    my $key = $1;
    print "Found key $key\n";
}

[download]
Also look at Regex::PreSuf which builds a better regex from a list of words.

Of course... if you always have a set delimeter you can do something like 

my @values = split ',', $filename;

for(@values) {
  print "Found key $_\n" if $list_of_keys{$_};
}

[download]
That is a better way to do it if you have something you can split on reliably

                - Ant
                - Some of my best work - (1 2 3)

In reply to Re: Testing for the presence of a hash key in a filename by suaveant
in thread Testing for the presence of a hash key in a filename by NovMonk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.