From: Yukihiro Matsumoto <matz@...>
Date: 2004-12-04T01:19:38+09:00
Subject: Re: GC run at end of script execution - order in which objects are claimed?

Hi,

In message "Re: GC run at end of script execution - order in which objects are claimed?"
    on Sat, 4 Dec 2004 01:07:25 +0900, Tilman Sauerbeck <tilman@code-monkey.de> writes:

|In my Ruby extension, there are "parent" objects and "child" objects.
|The "parent" object must not be freed if there are still "child" objects
|alive. I enforce this policy by using rb_gc_mark(). This seems to work,
|cause there are no problems as long as the ruby script executes.
|
|However, when I quit the application, the GC seems to break this policy.

Yes, GC calls destructors (dfree) in random order.

Questions:

Is it OK to terminate the process without any freeing?
Or is it mandatory to destruct objects in certain order?

							matz.