Yep-- use open(). Like so: 
use File::Copy;

open(PROGRAM_OUT, "| $runbin/$program.x") 
    or die "Couldn't open '$runbin/$program.x': $!; stopped";
copy(\*STDIN, PROGRAM_OUT) or die "Couldn't copy: $!; stopped";
close(PROGRAM_OUT) or die "Error while closing: $!/$?; stopped";

[download]

Untested.

That runs your FORTRAN process, copying STDIN to it, then checks the error code on file close.

Update: Actually, system() by itself should work fine... it inherits your STDIN from the main program. So if you get rid of the redirection and temporary file, it should work fine. So just 

system("$runbin/$program") == 0
    or die("'$runbin/$program' failed: returned signal @{[ $? >> 8 ]} 
+stopped";

[download]

stephen

In reply to Re: Split STDIN Pipe by stephen
in thread Split STDIN Pipe by murphya

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.