That makes sense. I understand what you mean that the discrepancies will be much lesser with smaller inputs. In fact, I have seen that happen with my tool too. Considering I'm using Parallel::ForkManager now (please see Update 2 of my original post), I should be able to implement this idea relatively easily.

But I won't be able to modify the output of the tool. As I mentioned in my other post, I cannot edit this tool in anyway. So I guess I will still have to deal with multiple files, which is not too much of a problem though. I can use a specific prefix for the output files generated by a single input, and merge them later. Not the best way, but certainly an easier way (given the noob I am).

Will update how it goes. Thanks a lot for the detailed explanation.

In reply to Re^4: Wait for individual sub processes by crackerjack.tej
in thread Wait for individual sub processes [SOLVED] by crackerjack.tej

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.