From: Aaron Patterson <aaron@...>
Date: 2009-10-08T05:38:11+09:00
Subject: [ruby-core:26002] Re: Disabling tainting

On Oct 7, 2009, at 7:59 AM, Kornelius Kalnbach wrote:

> Tony Arcieri wrote:
>> That's fine, but 99.9% of Ruby programs out there don't use it and it
>> impacts performance, so isn't making it an on-by-default
>> configurable option a good idea?
> I would find it confusing to have Ruby versions with different  
> features.
> code that works on one Ruby would no longer work on the
> Ruby-w/o-tainting version, or the other way round. it's complictaed
> enough to have Ruby 1.8.6, 1.8.7, and 1.9.1 for now.
>
> so, no, in my view it would not be a good idea to use a compile-time
> switch that make Rubys with different feature sets.
>
> but it would still be very interesting to measure the performance  
> impact
> of some features :)
>
> does JRuby have such a switch?

No.  JRuby just doesn't implement $SAFE.

     [apatterson@higgins ~]$ ~/Downloads/jruby-1.3.1/bin/jruby - 
e'$SAFE = 1'
     -e:1 warning: SAFE levels are not supported in JRuby
     [apatterson@higgins ~]$

---
Aaron Patterson
http://tenderlovemaking.com