[ruby-core:25953] Re: Disabling tainting

Switching off taint checking at runtime doesn't make sense, because it 
adds an additional check ("do we have to do taint checking") in case 
it's on, and keeps the same number of checks (one check; "do we have to 
do taint checking" instead of "is the object tainted") if switched off.

The way to gain some (probably not much) time would be a compile-time 
switch. I can't speak for Matz or Nobu, but I guess if you submit a 
patch, and give some actual numbers of time saved, there's some chance 
it would be accepted.

Regards,   Martin.

On 2009/10/06 3:45, Kornelius Kalnbach wrote:
> Tony Arcieri wrote:
>> The goal would be to eliminate the performance losses caused by this
>> esoteric and not particularly useful feature.
> do you have benchmarks that show how much performance is lost by taint
> checking? I'd assume it's not even measurable.
>
> [murphy]
>
>

-- 
#-# Martin J. Dst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:[e-mail]