Vlad, > > More information on the bug: for me %ENV is cleared if NO commandline arguments > > are passed. If I pass any commandline argument, %ENV is preserved (and is > > extended with those 3 special vars). > > This bug is a blocker for me. > > Could anybody at least state whether this problem is reproduceable on your > systems? With current version of PAR? With versions of perl other than 5.6.1?
I suspect this bug is closely correlated with a bug my colleague Tom Pollard reported on my behalf some months ago: the loss of very short command-line arguments supplied on the pp extract-and-run command line. We found that a single command-line argument of 1 or 2 character length was sometimes not present in perl's @ARGV. We could never establish the "rule" describing when the loss would occur, and when it wouldn't, but we could sometimes influence the behavior by tweaking env variables just before pp run time. We later observed other strange behavior -- only sometimes -- when pp was run with no arguments, which is almost certainly due to the exact same bug you are seeing now. The erratic problems are observed on a variety of OS's -- Linux, IRIX, AIX -- so the cause is not OS-specific. We see the problems using perl 5.8.1, so the cause is no doubt in pp or perl (or both) code which hasn't changed recently. FWIW, in one of our major uses of pp here, we work around the issue by always running pp with a dummy argument supplied, which the packaged perl script expects to find, and then does nothing when it finds it. -- Mark
