foreach (keys %fhs)
    {
        my $fh = $fhs{$_};

        if ($_ =~ /\.h\.new$/)
        {
        print $fh "#endif\n";
        }

[download]
The whole point of $_ is that of being the topicalizer: you either want 
for my $file (keys %fhs) {
    # ...
    print $fh whatever
      if $file =~ /\.\.new$/;
}

[download]
or 
for (keys %fhs) {
    # ...
    print $fh whatever
      if /\.\.new$/;
}

[download]
but your mixed form doesn't add to code readability, although -of course- it is not illegal. (I also took the liberty of rewriting the if condition as a statement modifier, as IMHO it is clearer that way.)

In reply to Re: handling multiple file handles for code generation by blazar
in thread handling multiple file handles for code generation by danmcb

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.