It's not clear from your question if you want to do additional processing in perl after you get the output from foo. If you get to the point of needing pipes to and from a command, I suggest you look at IPC::Run, which is reputed to be safer than IPC::Open2 or IPC::Open3. Here is some example code adapted from the IPC::Run man page: 
use strict;
use IPC::Run qw( start finish ) ;
my @cat = qw( cat ) ;
# Create pipes for you to read / write (like IPC::Open2 & 3).
my $h = start
       \@cat,
       '<pipe', \*IN,
       '>pipe', \*OUT,
       '2>pipe', \*ERR
       or die "cat returned $?" ;
print IN "some input\n" ;
close IN ;
print <OUT>, <ERR> ;
finish $h ;

[download]

In reply to Re: Confusion with two-way pipes by tall_man
in thread Confusion with two-way pipes 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.