On Tue, Aug 01, 2000 at 11:56:48AM -0400, Dan Sugalski wrote: > What I was thinking of was something along the lines of a lexically scoped > pragma--"use taint"/"no taint". (We could do this by sticking in an opcode > to set/unset the tainting status, as well as the warning status, and so on) > Taint checking is disabled in a no taint block. Whether we still set the > taint status on a scalar could depend on the -T switch, so data would still > be tainted in a no taint block. I agree with a pragma. But I think there should be some distinction between taint setting and taint checking. Graham.
- Re: RFC: On-the-fly tainting via $^T Bryan C . Warnock
- Re: RFC: On-the-fly tainting via $^T Graham Barr
- Re: RFC: On-the-fly tainting via $^T Simon Cozens
- Re: RFC: On-the-fly tainting via $^T John Tobey
- Re: RFC: On-the-fly tainting via $^T Dan Sugalski
- Re: RFC: On-the-fly tainting via $^T Matthew Cline
- Re: RFC: On-the-fly tainting via $^T Dan Sugalski
- Re: RFC: On-the-fly tainting via $^T Nathan Torkington
- Re: RFC: On-the-fly tainting via $^T Chaim Frenkel
- Re: RFC: On-the-fly tainting via $^T Dan Sugalski
- Re: RFC: On-the-fly tainting via $^T Graham Barr
- Re: RFC: On-the-fly tainting via $^T Dan Sugalski
- Re: RFC: On-the-fly tainting via $^T Graham Barr
- Re: RFC: On-the-fly tainting via $^T Ariel Scolnicov
- Re: RFC: On-the-fly tainting via $^T Nathan Wiger
- Re: RFC: On-the-fly tainting via $^T Tim Bunce