Front page | perl.perl5.porters |
Postings from October 2012
If I may add my word, I think the taint mode is a very valuable part of the Perl interpreter, very useful, and typically something you miss when you write in another language. As Vincent said, I feel that documenting it would appear as a way to endorse it, and a way to make a faster Perl. Others compared the taint mode with thread support or PerlIO support. They are a bit different though, because all these other features are enabled by loading modules, while the taint mode is enabled via a command-line option. All the options recognized by perl (except -D) activate features which are available in any default version of the interpreter since so many years that they are as well, in a sense, part of the language. Steffen Mueller wrote: > It's a warning that would be useful in pre-production, not production. So it's not too late. Furthermore, I think there's a class of cases where such a warning is fine. It's not silent. If you run a script that actually makes real use of -T, you'll know. But it doesn't prevent various test suites of CPAN modules from running just because they author figured -T would be a good idea in a test's shebang. Even if it's part of a cargo cult, it's good cargo cult. The CPANTS Kwalitee Game was invented for this: to give people the incentive to strengthen their code, for example by using strict, warnings and taint, by adding tests and examples. A couple of years later, the overall quality of the code on the CPAN has improved thanks to this. I don't have stronger arguments, except than making a well-known option lie doesn't "feel" right. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.Thread Previous | Thread Next