I have found that par is highly sensitive to the surrounding perl install. I use it on my machine all the time, and the executeables work flawlessly on any machine they're deployed on. However, I have a coworker and executeables created by par on his machine are a downright nightmare. Only maybe 1 in 5 works on any other machine at all, and often the generated executeables require perl56.dll. This is especially odd since the executeables produced on my machine tend to be significantly smaller (10% or so) than the ones produced on his, for the same script.

Now, in theory we're both using the same version of ActiveState's perl, and the same version of PAR. However, his is installed in some personal subdirectory (something like C:\Stuff\Perl), and I think there might be some weird permissions issues with it too. Mine was installed, from a clean system, straight into C:\Perl.

@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/;
map{y/X_/\n /;print}map{pop@$_}@/for@/
[download]