If you would like to invoke two separate shell scripts in a single shell session, try this -- at least, this is how I would do it on *nix... Frankly, I'm not sure this can be done in a windows environment, but it might be worth a try: 
open( SH, "| /path/to/bash" ) or die "Can't open a shell: $!";
my @scripts;
{
  local $/ = undef;
  for my $file ( "first_shell_script", "second_shell_script" ) {
      open( SCR, $file ) or die "couldn't read $file: $!";
      push @scripts, <SCR>;
      close SCR;
  }
}
print SH $scripts[0];
print SH $scripts[1];

# and then do whatever magical stuff this shell can do,
# now that it has these scripts in its arsenal...

[download]

In reply to Re: Creating bash functions using perls $ENV interface by graff
in thread Creating bash functions using perls $ENV interface by tid

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.