Re: perl -T script.pl and #!/usr/bin/perl -T conflict

I assume you mean the 'Too late for "-T" option at script.pl line 1.' error. This happens because you have run perl without -T, then when it examines the #! line and sees -T, it realizes you want tainting, but it is too late. You need to make sure -T is passed when using 'perl script.pl'. I know of no way around this, as opposed to aliasing 'perl' with 'perl -T' or some similar lunacy.

Cheers,
KM

Comment on Re: perl -T script.pl and #!/usr/bin/perl -T conflict

Replies are listed 'Best First'.
Re: Re: perl -T script.pl and #!/usr/bin/perl -T conflict by arturo (Vicar) on Jan 24, 2001 at 23:42 UTC
Neat related idea (and you know, I have princepawn to thank for making me think about this in the first place) -- you could also have a batch file (as you explained in the CB, you're worried about porting to win32), that calls `perl.exe -T %1` (or however that's done =), call it (say) `perlrun.bat`, stick it in your PATH, and call the script as `perlrun script.pl` Philosophy can be made out of anything. Or less -- Jerry A. Fodor	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: perl -T script.pl and #!/usr/bin/perl -T conflict
by arturo (Vicar) on Jan 24, 2001 at 23:42 UTC

Neat related idea (and you know, I have princepawn to thank for making me think about this in the first place) -- you could also have a batch file (as you explained in the CB, you're worried about porting to win32), that calls perl.exe -T %1 (or however that's done =), call it (say) perlrun.bat, stick it in your PATH, and call the script as perlrun script.pl

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

[reply]
[d/l]
[select]