open (XX, "perl -w test_two.pl |");
my @test = <XX>;
close (XX);
[download]

my @test = `perl -w test_two.pl`;
[download]

my $output = `perl test_two.pl`;
print $output;
[download]

Read through perldoc -f eval. The following shows a quick demo.

#!/usr/bin/perl

use strict;
use warnings;

open FILE, "test1.pl" or die "Cannot read test1.pl: $!\n";
my $file = join '', <FILE>;
close FILE;

eval $file;

# Check for errors.
die $@ if $@;
[download]

Wouldn't it be much simpler to do something along the lines of;

do "test.pl";

tlhf

That is, if 'test_two.pl' prints something and you just want to forward that print, you can execute your program with do for that.

If program number two is returning something, you can capture the result from do and print that.

Example code:

## test_one.pl:

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

# $bar will hold "Bar", 
# "Foo" gets printed right away.
my $bar = do 'test_two.pl';

print $bar;

## test_two.pl:

print "Foo\n";

return "Bar\n";
[download]

This is a somewhat faulty solution in case you want to mangle the output from the second script, but if you don't, this is the simplest way, without executing external programs or reading files and evaling.

I think that you would be better off looking at the documentation for require rather than using eval. If your first program looks like this.

#! perl -sw
use strict;

require 'test2.pl';

print weather();
[download]

And your second program like this (test2.pl)

#! perl -sw
use strict;

sub weather {
    # do stuff to gen data
    return 'This is the generated data';
}

1;
[download]

When test1.pl is run it gives the following output

C:\test>test
This is the generated data
C:\test>
[download]

If you want to execute an external perl script, you can use the

command (check your perldoc -f do).

This will evaluate EXPR and take it's result as the filename to execute.

You should not use qx`` (backticks), unless you need to pass arguments, or need control over the scripts output. It's more expensive than just do-ing the script. Apart from the pipeing overhead, calling the other script using backticks would start another perl instance to run it -- which will demand extra memory, of course.

Same applies to opening a pipe to the external script, the way kabel sugested. Update: You only want to use pipes if you need to input to the other script's STDIN.

So long,
Flexx

$test = `test_two.pl`;
[download]