It's very easy to say "well, you can do taint checking without taint mode on". And yes, you are right. But your comment "such a thing wouldn't likely occur to someone who knows what they are doing." is counter-intuitive.
A good programmer thinks not only of what (s)he is capable of, but also that the code will be maintained in the future -- maybe by someone else. Not using tainting invites three forms of disaster:
- Mistakes in untainting (this is analogous to why good programmers use strictures)
- Tainting introduced accidentally during a "quick revision"
- Tainting introduced by another developer during maintainance.
If all one is doing involves validating a name and email address or some such simplicity, then perhaps tainting isn't absolutely necessary
, but when one is dealing with large amounts of data, it is.
For this solution, the performance hit is quite tiny. In large environments where performance would be a significant issue, one would likely be able to make the case with the admin staff to set up a perl -T association.
.oO all things connect through the motion of the mind
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.