On 06/05/2012 08:29 AM, Mattias Gaertner wrote:
yes it is relevant. If you have two memory managers you can not
exchange strings and classes.
Is cmem "the way to go" to unify the memory managers of a dynamic
library and the calling application ? (There seem more advanced free
alternatives written for Delphi, that might be usable with FPC.)
Will just "using" cmem both in the main program and in the library
automatically unify the memory managers ?
http://wiki.freepascal.org/Multithreaded_Application_Tutorial states:
cmem, // the c memory manager is on some systems much faster for
multi-threading
and
You can not use the -gh switch with the/cmem/ unit. The -gh switch uses the
heaptrc unit,
which extends the heap manager. Therefore the*heaptrc* unit must be
used*after* the*cmem* unit.
Should the FPC memory manager not be more optimized for FPC code then cmem ?
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
