Re^2: ARGV Problem (pl2bat++)

I use pl2bat (included in Win32-perl's 'bin' directory) and so don't have to worry about this. But it is more because you shouldn't have to know what language tool X is written in just to use X. So I never run perl scripts via "script.pl ..." nor via "perl script...".

I've rewritten tools between Perl, *.cmd, C++, etc. and don't need to retrain my fingers much less have to find and update other tools that happen to use the rewritten tool.

- tye

Comment on Re^2: ARGV Problem (pl2bat++)

Replies are listed 'Best First'.
Re^3: ARGV Problem by pKai (Priest) on Jan 07, 2006 at 08:56 UTC
...nor via "perl script...". Well, you do... your pl2bat generated batch files do it for you... I see your point, but as someone who long abandonded maintaining dual language scripts (since my change from using Perl5 instead of Perl4 and using WinNT, which gave me a way to just declare .pl files "executable") and someone who is supposed to support Win at work, I prefer not to ignore this "1 in a million" problem, but seek for a proper explanation/fix.	[reply]

Replies are listed 'Best First'.

Re^3: ARGV Problem
by pKai (Priest) on Jan 07, 2006 at 08:56 UTC

...nor via "perl script...".

Well, you do... your pl2bat generated batch files do it for you...

I see your point, but as someone who long abandonded maintaining dual language scripts (since my change from using Perl5 instead of Perl4 and using WinNT, which gave me a way to just declare .pl files "executable") and someone who is supposed to support Win at work, I prefer not to ignore this "1 in a million" problem, but seek for a proper explanation/fix.

[reply]