|No such thing as a small change|
Has anyone seen perl losing arguments?by ted.byers (Monk)
|on Sep 28, 2011 at 18:58 UTC||Need Help??|
ted.byers has asked for the
wisdom of the Perl Monks concerning the following question:
It is hard to imagine how one can get this wrong, but the following is giving me grief on one machine (and only that one out of the several that I use).print "$ARGV\n\t$ARGV\n\t\t$ARGV\n";
This is obvious and well documented, and something I have used for years without problems. However, on a new server (hosted in the cloud, if that matters), it is failing in a manneer that is a show-stopper. The buld of Activestate Perl is:This is perl 5, version 14, subversion 1 (v5.14.1) built for MSWin32-x64-multi-thread
The problem is that with this particular machine, perl scripts invoked as:
loses the arguments. The above lines of code are the last in a driver script, and intermittently, the above lines of code behave as if the following had been executed instead:
It doesn't matter whether I am executing these programs using back ticks or using system, the behaviour is the same, but on this new machine, it happens about 80% of the time, and never on the other machines I use. That, especially, has me baffled.
Has anyne else seen this? If so, what is the fix? If not, does anyone have any ideas on how best to fix this?
I appreciate any help I can get