Hello, Mr. Tack:
Guido Tack <[EMAIL PROTECTED]> wrote: Vesa Karvonen wrote:
> On Fri, Mar 7, 2008 at 5:48 PM, Andreas Rossberg
> wrote:
>> Also, some libraries already replace allocation themselves, so that
>> it is not that easy to redirect. I believe that Gecode falls into
>> that category (Guido will correct me if I'm wrong).
>
> That would be evil. The rule of thumb is that only the "module" that
> implements main should ever replace (the global) new/delete.
Gecode does all its allocation through malloc, but doesn't reimplement
it. It just "bundles" everything at a single place so that memory
management can be reimplemented easily. So this would actually be an
option, to replace the Gecode allocation by a scheme that is GC aware.
Do you foresee that happening in the near future? Since you work on both
projects, you obviously have a better sense of what the undertaking would
involve.
I like Alice very much -- I don't want to give up its static typing for the
dynamism of Mozart, for example, or to leave SML to dip to C++ level to
directly call the Gecode API. But I was a bit worried that even constant
garbage collection had no effect on memory usage.
Nevertheless, thank you very much for all your work. Alice is invaluable for
what I do!
-- Thomas
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now._______________________________________________
alice-users mailing list
[email protected]
http://www.ps.uni-sb.de/mailman/listinfo/alice-users
