7rans
(7rans)
15 July 2011 18:22
1
I would seem there is no way to jack into the update of
$LOADED_FEATURES?
class << $LOADED_FEATURES
methods = public_instance_methods(true)
methods.each do |m|
alias_method "_#{m}", m
define_method(m) do |*a, &b|
p m, *a
send("_#{m}", *a, &b)
end
end
end
require 'ostruct'
=> true
?
Not from ruby as $LOADED_FEATURES is not updated through rb_gv_set() or rb_gvar_set()
···
On Jul 15, 2011, at 11:22 AM, Intransition wrote:
I would seem there is no way to jack into the update of $LOADED_FEATURES?
7rans
(7rans)
21 July 2011 14:56
3
Thanks.
I ended up just requiring that the user put there requires in a
special block so I could capture the changes to $LOADED_FEATURES.
See http://rubyworks.github.com/autoreload/
···
On Jul 20, 8:33 pm, Eric Hodel <drbr...@segment7.net> wrote:
On Jul 15, 2011, at 11:22 AM, Intransition wrote:
> I would seem there is no way to jack into the update of $LOADED_FEATURES?
Not from ruby as $LOADED_FEATURES is not updated through rb_gv_set() or rb_gvar_set()