From: "Zed A. Shaw" <zedshaw@...>
Date: 2005-09-12T12:59:26+09:00
Subject: Re: [RFC] The Early Demise of Myriad (Thanks To Ruby Threads)

On Mon, 12 Sep 2005 09:32:58 +0900
Wink Saville <wink@saville.com> wrote:

<snip>
> Thanks for the feed back and the gotcha's! Let me noodle on this a while 
> and then possibly start a discussions about my idea's.
> 
> One big worry that you've identified is the GC. In the current messaging 
> system we manage memory from a pool malloc'd once and never freed. So 
> would the following work: I register the entire pool as a single entity 
> with the GC. Then can create multiple ruby objects referring into the 
> pool. When Ruby is done an object will it try to "free" the object or 
> will it know that there is another reference and let me manage the memory?
> 

Actually, this would be the *best* way to do this.  You just register the whole damn pool with the GC and never unregister it.  Then you do your own memory management and control.  The GC is completely cut out of the picture and can't mess with your gear.  The only thing you need to do is just not declare a free function for the ruby object.

Zed A. Shaw
http://www.zedshaw.com/