I second what jethro said. Maybe use a Modulino (Example from 'Mastering Perl' - see link at end of article) ?

But since you asked... (because it is possible, not recommended): 

use strict;
use warnings;

our $exchange = "before (set by caller)";

my $other_file  = "this_other_thing.pl";
my ($out, $err) = redir_file( $other_file );

#-- proof of re-direction and import/export
print "Caller: GOT from STDOUT ($other_file): ",
  join("\n\tOUT>  ", "", split( /\n/, $out) ), "\n";
print "Caller: GOT from STDERR ($other_file): ",
  join("\n\tERR>  ", "", split( /\n/, $err) ), "\n";
print "Caller: Exchange : $exchange\n";


sub redir_file {
  my $do_filename = shift;

  #-- we DUP the current STREAMS and then we close the original stream
+s...
  open(my $oldout, ">&STDOUT")     or die "Can't dup STDOUT: $!";
  open(my $olderr, ">&STDERR")     or die "Can't dup STDERR: $!";
  close STDOUT;
  close STDERR;


  #-- now, we re-open the streams with redirection into strings...
  my $redir_stdout;
  my $redir_stderr;
  open( STDOUT, '>', \$redir_stdout ) or die "Cannot redirect STDOUT t
+o string: $!";
  open( STDERR, '>', \$redir_stderr ) or die "Cannot redirect STDERR t
+o string: $!";


  #-- this is like "do"... and exactly as insecure...
  my $do_file_content = qx{cat $do_filename};    # e.g. use Slurp...
  my $read            = eval $do_file_content;   # =8-O
  #... now $exchange might have been updated

  #-- now, we restore the previous streams...
  open(STDOUT, ">&", $oldout) or die "Can't dup \$oldout: $!";
  open(STDERR, ">&", $olderr) or die "Can't dup \$olderr: $!";

  return ($redir_stdout, $redir_stderr);
}

[download]

Modified this_other_thing.pl (our...) 

#!/usr/bin/env perl 
use strict;
use warnings;
use utf8;

our $exchange;

print STDOUT  "PRG: Hello World!\n";
print STDERR  "PRG: Hello Err!\n";
print         "PRG: Exchange: ", ( $exchange // '(nothing)'), "\n";

$exchange = "after (called program)";

[download]

Result: 

Caller: GOT from STDOUT (this_other_thing.pl): 
        OUT>  PRG: Hello World!
        OUT>  PRG: Exchange: before (set by caller)
Caller: GOT from STDERR (this_other_thing.pl): 
        ERR>  PRG: Hello Err!
Caller: Exchange : after (called program)

[download]

Don't know if this works well for Windows and in threaded/forked environments...

In reply to Re: I want to run a script from another script, use the same version of perl, and reroute IO to a terminal-like textbox by Perlbotics
in thread I want to run a script from another script, use the same version of perl, and reroute IO to a terminal-like textbox by ric00015

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.