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

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.

This would be helpful for extension writers. Would the method take a 
block, to turn on the feature only for suspect code?

GC.every_allocation
GC.aggressive
GC.eager
GC.leave_no_garbage_behind
GC.fanatically_tidy

Come on creative people, this is a softball question!

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