Say you have 2 values in the variables $foo and $bar. To run x.pl in another process:

$foo = 'whatever';
$bar = '42';
system $^X, 'x.pl', $foo, $bar; # run a new "perl script args"
[download]

to call x.pl from within the same perl interpreter:

$foo = 'whatever';
$bar = '42';
{ local @ARGV = ($foo, $bar); do 'x.pl' };
[download]

In both variants $foo and $bar are in @ARGV in x.pl.

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

thanks

Hi Monk,

Your answer really did, what I wanted.

Is it possible to return the output back into the calling script.

Like .. taking the above script as example i.e. 'x.pl' and its two values => $foo, $bar

Now I have another script lets call it 'y.pl'

Now from 'y.pl' I am calling 'x.pl' and simultaneously passing these values.

Then the output of 'x.pl' back to 'y.pl'. Something like 'return' does

Thanks For any help

I'm not really clear what you mean by "input". But have you looked at @ARGV in perlvar already? Or maybe you need to be more explicit in what you want - maybe you want to read the values from STDIN?

Scripts usually do not “call each other.”

Why not? Because there's a better way to do it. Build the various common functionality into one or more packages, then create scripts that invoke the routines and objects defined within the packages.

Once you're in a package-based environment, directives like use and require become readily-available to you. You're operating now in a single process (probably) and therefore the same instance of Perl. Now, you can use variables and other such things quite freely.

Yes, you can do things another way (TMTOWTDI™ ...), but always look-for what is the best available way in your particular situation. In other words, strive to look objectively at the goal and to consider all of the ways to fill it. Many's the time when I “jumped to a conclusion” and later discovered that I had just “jumped in the lake.” (Ooh, I hate it when that happens!)