From: SASADA Koichi <ko1@...>
Date: 2013-03-22T18:15:32+09:00
Subject: [ruby-core:53629] Re: [ruby-trunk - Feature #8107] [patch] runtime flag to track object allocation metadata

(2013/03/22 17:41), tmm1 (Aman Gupta) wrote:
> 
>> >  - `task' is ambiguous (all of procedures are task).
> Do you prefer `rb_delayed_task_*` and vm_delayed_task.c ?

I prefer rb_delayed_task_. but if there is more good name, suggestion.
I think vm.c is good place to put them.

>> >  - Allocation during gc is dangerous (maybe, should be prohibited)
> Yes, I thought of that when using ALLOC_N. Is it safe to use regular allocation (without xmalloc)? Or better to maintain static array or freelist?

I believe static sized C-array (for example, 128 entry) is enough for
this purpose. If overflow, then cause error.

-- 
// SASADA Koichi at atdot dot net