Hi,

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

|Since the random free'ing is causing sincere memory management problems
|in my extension, I'd say "yes". Although I think there must be some
|not-so-hard way to avoid this; there must have been extension developers
|who had the very same problem.

Oh, I got an idea.  How about making a parent free its children
objects eagerly in dfree function, then free itself?  You can use some
kind of flag to prevent double free.

							matz.