I think all you need to do is put a statement-ending semi-colon (;) after these two lines:

my $t1 = async { qx(perl process1); }
my $t2 = async { qx(perl process2); }
[download]

...so they look like this:

my $t1 = async { qx(perl process1); };
my $t2 = async { qx(perl process2); };
[download]

That's what it shows in the threads documentation, and works for me on one of my machines that has a threads capable perl.

-stevieb

$ perl -MO=Deparse
#!/usr/bin/perl

use strict;
use warnings;
use threads;

my $t1 = async { qx(perl process1); }
my $t2 = async { qx(perl process2); }

my @out1 = $t1->join;
__END__
Global symbol "$t1" requires explicit package name at - line 10.
- had compilation errors.
use threads;
use warnings;
use strict;
my $t1 = async(sub {
    `perl process1`;
}
, my $t2 = async(sub {
    `perl process2`;
}
, my(@out1) = ${'t1'}->join));
[download]

threads doc's have two potentially interesting things to say, that may just help.

firstly, you seem to missing a semicolon or two.

async BLOCK;
        "async" creates a thread to execute the block immediately foll
+owing
        it. This block is treated as an anonymous subroutine, and so m
+ust have
        a semicolon after the closing brace.
[download]

also

Threads are implemented in a way that make them easy to misuse.
Few people know how to use them correctly or will be able to provide h
+elp.

The use of interpreter-based threads in perl is officially discouraged
+.
[download]

And, once you know it, it's easy to duplicate the error:

c:\@Work\Perl\monks>perl -wMstrict -le
"sub foo (&@) { return 42; }
 ;;
 my $x = foo { }
 print $x;
"
Global symbol "$x" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
[download]

Yeah nothing specific about threads, just the fact that my declarations only start being effective after the next semicolon.

This was done to allow constructs like

my $x = $x++;

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}

When I first read LanX's reply, I was confused because the statement all on its own is an error. But LanX /msg-ed me that the rule allows access to same-named lexicals in surrounding scopes:

c:\@Work\Perl\monks>perl -wMstrict -le
"my $x = 42;
 if ($x) {
   my $x = $x++;
   print $x;
   }
 print $x;
"
42
43
[download]

Now I understand.

---

Give a man a fish:  <%-{-{-{-<