From: Roger Pack <rogerdpack2@...>
Date: 2010-03-24T02:44:44+09:00
Subject: [ruby-core:28894] Re: [Feature #1047](Feedback) request: getters, 	setters for the GC

>> My personal opinions:
>>
>> - Though I think a few rough "modes" is acceptable (e.g., -server and
>> �-clients of Java), such a specific parameter tuning is not Ruby way.


Here are a couple of options:

parameter flags, like
 --gc_often
 --gc_seldom

or
GC.gc_often!
GC.gc_seldom!

(or whatever verbs you want to use).

My own preference would be to still have access to the guts of the GC
during runtime--even if it's very implementation specific it would
still be useful, I think, in some cases, to have access.  Maybe
there's a way to make it more clear that they're implementation
specific, like putting them under RubyVM?

Thoughts?
-rp


>
> That seems reasonable. �Maybe like --conservative or --server or what not.
>
>
>> - The name `malloc_limit' is very arguable because it is too specific
>> �to implementation-detail of MRI.
>
> agreed.
>
> -rp
>
>