Your next step is to inspect what is in %CONFIG_FILE when you encounter that condition.

Use the following code:

if ($file =~ /$key/) { $mapattach = $value; use Data::Dumper; print Dumper \%CONFIG_FILE; }

Also output whenever you get a match on /$key/:

if ($file =~ /$key/) { $mapattach = $value; use Data::Dumper; print Dumper \%CONFIG_FILE; print "'$file' matches /$key/, setting value '$value'\n"; }

Maybe there are two keys in %CONFIG_FILE that match the filename and the second one overwrites the first match in some cases? You are aware that hash keys are not ordered in Perl?


In reply to Re^4: Code Issue after Upgrading the perl from 5.14.4 to 5.22.3 by Corion
in thread Code Issue after Upgrading the perl from 5.14.4 to 5.22.3 by Srinath

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.