• bearophile <bearophileHUGS lycos.com> Aug 15 2010
• Jonathan M Davis <jmdavisprog gmail.com> Aug 15 2010

bearophile <bearophileHUGS lycos.com> writes:

Max Samukha:
 We tried to impose management of all QtD objects on the user but that 
 proved to be a bad idea. The exception is QObject. In Qt QObjects are 
 arranged in trees. When the root node is destroyed all its children are 
 destroyed as well. GC is disabled for QObjects.


I think Phobos2 can enjoy a semi-manual overarching memory allocator, like
halloc.

Bye,
bearophile

Jonathan M Davis <jmdavisprog gmail.com> writes:

On Sunday 15 August 2010 10:10:29 bearophile wrote:
 Max Samukha:
 We tried to impose management of all QtD objects on the user but that
 proved to be a bad idea. The exception is QObject. In Qt QObjects are
 arranged in trees. When the root node is destroyed all its children are
 destroyed as well. GC is disabled for QObjects.


 I think Phobos2 can enjoy a semi-manual overarching memory allocator, like
 halloc.
 
 Bye,
 bearophile


Cry halloc! and let slip the dogs of war.

- Jonathan M Davis


Okay, I honestly have no idea what halloc is, but I just had to say that.  I 
_have_ been accused from time to time of loving puns too much though...