Cool idea but if you read the question carefully: 
   # print $fn, $ln and $id to OUTPUT_A if $id = @a[0,1,2...n]
   # elsif print $fn, $ln and $id to OUTPUT_B if $id = @b[0,1,2...n]
   # elsif print $fn, $ln and $id to OUTPUT_C if $id = @c[0,1,2...n]

[download]
The way you are doing it both Homer and Clark end up in "b.txt". The way the question was written Homer should wind up in "a.txt" and Clark in "b.txt". All you have to do is reverse the order you fill your %data hash. 
@data {@c} = ($fh_c) x @c;
@data {@b} = ($fh_b) x @b;
@data {@a} = ($fh_a) x @a;

[download]
Now the code works as the question was asked.

--

flounder

In reply to Re: Re: A Love/Hate Relationship - A Long Time Newbie's Current Block by flounder99
in thread A Love/Hate Relationship - A Long Time Newbie's Current Block by bivouac

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.