Re: Non-overridable and non-redefinable methods

On 19 Aug 2005, at 12:32, Eric Mahurin wrote:

> --- Eric Hodel <[e-mail]> wrote:
>> Also, we couldn't make dead-simple proxies like this:
>>
>> class BlankSlate
>>    instance_methods.each { |m| undef_method m unless m =~
>> /^__/ }
>> end
>>
>> class Proxy < BlankSlate
>>
>>    def initialize(obj)
>>      @obj = obj
>>    end
>>
>>    def method_missing(sym, *args, &block)
>>      @obj.__send__(sym, *args, &block)
>>    end
>>
>> end
>>
>> class Foo
>>    def x; y; end
>>    protected
>>    def y; @y = :stuff; end
>> end
>>
>> foo = Foo.new
>> dfoo = Proxy.new foo
>>
>> p foo.protected_methods
>> p dfoo.protected_methods
>>
>> p dfoo.send :x
>> p dfoo.instance_variables
>>
>
> You couldn't do this - unless the only
> non-overridable/removable methods were __send__ and __id__ -
> because the above code didn't want to mess with them.
>
> This is a performance vs. flexibility tradeoff.  You'd want to
> find the right list of non-overridable/removable methods to
> give the best balance.

I'd trade BlankSlate proxies for speed any day of the week.  Ruby's  
current speed pays the bills without making the servers sweat, so I  
don't see what more speed gives me when I have to throw away  
flexibility.

-- 
Eric Hodel - [e-mail] - http://segment7.net
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04