Running external programs is done with open, system, exec, or "backticks" (the qx// operator). You can save some file manipulations if you don't write an intermediate file and then rename and modify it. User input can be read from STDIN. Here's a sketch, 

for (1..25) {
    warn "File Exists: $_.txt\n" and next if -f "$_.txt";
    print 'My prompt message: ';
    chomp(my $input = <STDIN>);
    open my $fh, '>', "$_.txt"     or warn $! and next;
    open my $ph, '-|', $cmd, $input or warn $! and next;
    {
        local $_;
        while {<$ph>) {
            do_your_processing($_);
            print $fh $_ or die $!;
        }
    }
}

[download]
You should see that this needs to be fleshed out by all your unspecified requirements.

After Compline,
Zaxo

In reply to Re: Running C++ multiple times and saving the output by Zaxo
in thread Running C++ multiple times and saving the output by Anonymous Monk

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.