On Fri, 16 May 2008 14:54:32 -0700, "Curt Hagenlocher"
<[EMAIL PROTECTED]> said:
> Do you have any feeling for how these programs are using
> thread.critical=?
It's used by just one method in activesupport, instance_exec (which
seems to be a built-in method in Ruby 1.9). Here is the method from
active_support\core_ext\object\extending.rb:
unless defined? instance_exec # 1.9
module InstanceExecMethods #:nodoc:
end
include InstanceExecMethods
# Evaluate the block with the given arguments within the context of
# this object, so self is set to the method receiver.
#
# From Mauricio's
http://eigenclass.org/hiki/bounded+space+instance_exec
def instance_exec(*args, &block)
begin
old_critical, Thread.critical = Thread.critical, true
n = 0
n += 1 while respond_to?(method_name = "__instance_exec#{n}")
InstanceExecMethods.module_eval { define_method(method_name,
&block) }
ensure
Thread.critical = old_critical
end
begin
send(method_name, *args)
ensure
InstanceExecMethods.module_eval { remove_method(method_name) }
rescue nil
end
end
end
Cheers,
Brian
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
