[#62904] [ruby-trunk - Feature #9894] [Open] [RFC] README.EXT: document rb_gc_register_mark_object — normalperson@...
Issue #9894 has been reported by Eric Wong.
3 messages
2014/06/02
[#63321] [ANN] ElixirConf 2014 - Don't Miss Jos辿 Valim and Dave Thomas — Jim Freeze <jimfreeze@...>
Just a few more weeks until ElixirConf 2014!
6 messages
2014/06/24
[#63391] Access Modifiers (Internal Interfaces) — Daniel da Silva Ferreira <danieldasilvaferreira@...>
Hi,
3 messages
2014/06/28
[ruby-core:63056] Re: [RFC] README.EXT: document rb_gc_register_mark_object
From:
SASADA Koichi <ko1@...>
Date:
2014-06-10 08:52:40 UTC
List:
ruby-core #63056
(2014/05/31 4:56), Eric Wong wrote: > +void rb_gc_register_mark_object(VALUE val) > + > + Tells GC to protect the object referenced by val. This requires less > + memory to track than rb_global_variable, but may only be used if the C > + variable never changes. > + How about that? > Tells GC to protect the object referenced by val. Another things are implementation details. And I'm not sure the following sentence is needed. > but may only be used if the C > variable never changes. I think it may assume global variables. But this API is independent from C's global variables. I think this comment may be for `rb_global_variable' users, but it is different API. PS. For our MVM development, we can not support "rb_global_variable()". So I want to make it obsolete. This is why I introduce rb_gc_register_mark_object(). But not yet. -- // SASADA Koichi at atdot dot net