Front page | perl.perl5.porters |
Postings from October 2012
On Mon, Oct 22, 2012 at 01:28:50PM -0400, David Golden wrote: > On Mon, Oct 22, 2012 at 7:37 AM, Ed Avis <eda@waniasset.com> wrote: > > > > If you really know what you're doing and you want to just ignore these flags, > > running with taint turned off even though it was specified on the command line, > > then this can trivially be done by writing a script that wraps the perl > > executable. IMHO, it is better to do it that way rather than adding the > > dangerous ignore-taint feature to the perl binary itself. > > You don't understand the patch. > > The *cost* of taint checks exists in the source regardless of whether > taint is turned *on*. There are a number of places that effectively > have a "is taint on? if so do X" code path. > The patch would compile out all those conditional checks. > > Wrapping wouldn't do anything. I think he is referring to writing a wrapper for the version of perl that you compiled without taint support, but which throws an error if you try to use it with -T. This would still have the efficiency gains without requiring a separate option for disabling that error. -doyThread Previous | Thread Next