It has to do with flushing the output buffers, which happens automatically when you write to the console but not to your special handles.

Try adding this at the top of your outerr.pl: 

use IO::Handle;
STDOUT->autoflush(1);
STDERR->autoflush(1);

[download]
Update:Also, IPC::Run is reputed to be safer to use than IPC::Open3. Here is how it would look: 
use strict;
use IPC::Run qw(run);

my @com = qw(outerr.pl);
my ($in, $out);
run( \@com, \$in, \$out, \$out);
print $out;

[download]
(Sad to say though, neither this version nor the one by BazB seems to give the interleaved output you want, even with autoflush turned on, on my Linux box. All the STDOUTs come before all the STDERRs).

In reply to Re: IPC::Open3 confusion by tall_man
in thread IPC::Open3 confusion by xafwodahs

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.