Depends on what you are doing with these two scripts. It might be time to rethink your design. Maybe what you really want to do is create a package with some functions and variables and then put the program logic into a second script.

#MyModule.pm
package MyModule;
use strict;
our $variable = 'hello!';
[download]

#MyScript.pl
use strict;
use MyModule;
print $MyModule::variable;
[download]

Also, you can use Exporter if you want to add optionality to your exports.

#!/usr/bin/perl
my $name = `perl1.pl`;
[download]

There are a variety of ways, depending on your goal. Here's one way (minus error checking and meta-character escaping):

$ cat script1.pl
#!/usr/bin/perl
# script1.pl

my $name = '123abc';
my $results = `./script2.pl "$name"`;
# $results now contains the output of script2.pl



$ cat script2.pl
#!/usr/bin/perl
# script2.pl

# run locate on the first argument given to this script
print `locate "$ARGV[0]"`;
[download]

Sorry all, thanks for the help thus far, but let me be more specific. Perl Script #1 has a variable, let's call it $final. $final is defined by user input, so it is always dynamic. I would like to use the input from $final in Perl Script #1 and use it to pass that input into Perl Script #2. Thanks.

My example does that, except that my variable is named $name instead of $final. I assigned a static string to mine, but you could get a value into $name using any dynamic method you like, and then pass it to a subprocess (written in Perl or any other language) on the command line using backticks as I did.

Aaron B.
Available for small or large Perl jobs; see my home node.

$final is defined by user input, so it is always dynamic.

Well, variables are always dynamic, that's why they are called variables.

Some of the confusion in the replies to your question seem to be caused by the term "script", which you are using. My understanding is, that script1 and script2 MUST be separate process, in the sense of independent commands, and you need to pass information from one script to the other. Is this correct?

Some replies to your question imply that there is a closer coupling of the script possible (so that you can run the whole code within a single process). Both approaches make sense, but maybe you should explain more in detail what your requirements are. Only then can we propose a better solution. Also it helps if you explain, what kind of value $final is supposed to have. Proposed solutions might be slightly different, dependent on whether this value, for instance, is supposed to be a one-digit number, or the content of a whole Word document...
-- 
Ronald Fischer <ynnor@mm.st>

Or just use the ‘obvious’ solution: save $final to a temporary file?

# in Script #1:

my $file = 'script1_final.txt'; # add path as required
open(my $fh, '>', $file) or die "Cannot open file '$file' for writing:
+ $!";
print $fh $final;
close $fh;

# in Script #2:

my $file = 'script1_final.txt'; # add path as required
open(my $fh, '<', $file) or die "Cannot open file '$file' for reading:
+ $!";
my $final = <$fh>;
close $fh;
unlink $file             or warn "Cannot delete file '$file': $!";

# Use $final as needed...
[download]

The only coupling required here is that the name of the shared file must be known to both scripts.

Not saying this is the best solution, but it does have the virtues of simplicity and extensibility (since it is straightforward to add data to the file if additional data sharing between the scripts is required down the track).

HTH,