Front page | perl.perl5.porters |
Postings from October 2013
So where would this be documented? Before reporting this issue I checked the relevant man pages, my dead tree copy of the camel, and google; so if this is not a bug in the code as you assert, might it be something that needs to be documented? On Tue, Sep 17, 2013 at 4:51 AM, Zefram via RT <perlbug-followup@perl.org>wrote: > ben@hildred.us wrote: > >When running under taint mode the first works, but the second does not > > Not normally regarded as a bug. Perl's taint checking deliberately > doesn't track data flows in a fine-grained manner, because that would > be much more expensive (even for programs not using tainting). Once a > statement has read a tainted variable, the whole statement is tainted, > so it can't perform unsafe actions and its outputs are tainted. You've > written the same logic in a two-statement form and in a one-statement > form, so the difference in tainting behaviour is expected. > > -zefram > > > -- -- Ben Hildred Automation Support Services 303 815 6721Thread Previous | Thread Next