From: Joel VanderWerf <vjoel@...>
Date: 2005-12-20T04:52:04+09:00
Subject: Re: ruby-dev summary 27761-28026

Eric Hodel wrote:
> On Dec 19, 2005, at 11:08 AM, ara.t.howard@noaa.gov wrote:
> 
>> On Tue, 20 Dec 2005, Joel VanderWerf wrote:
>>
>>> SASADA Koichi wrote:
>>> ...
>>>
>>>> [ruby-dev:27991] GC.always
>>>> Akira Tanaka proposed "GC.always" method.  This method forces ruby
>>>> interpreter to invoke GC whenever it is invokable.  It means that GC
>>>> will be invoked at every object allocations, every memory  allocations.
>>>> This feature helps interpreter debugging around GC bugs.
>>>> Matz refused "GC.always" method name (didn't refused this  feature, 
>>>> only
>>>> method name).  Another proposed method name is "GC.debug".
>>>> This issue is still open.
>>
>>
>> i really, really prefer an options based approach to these kinds of  
>> things.
>> when you have to pick a name for every method the development is  
>> slowed.  pick
>> a catch-all and configure it:
>>
>>   GC.gc(:mode => "every") do
>>
>>   end
>>
>>
>> next week, when someone wants a new feature, it can be added it  without
>> changing a thing:
>>
>>   GC.gc(:mode => "every", :pool => MyCustomPool) do
>>
>>   end
> 
> 
> YAGNI
> 

YAGN what? GC.always or an options hash?

-- 
        vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407