I think that oleg meant malloc is different for different compilers, but in
linux world there is only one compiler - gcc, so that it is safe to mix modules
compiled separately.
Raul Miller wrote:
On 4/13/07, Oleg Kobchenko <[EMAIL PROTECTED]> wrote:
In C runtime library malloc/free use private local heaps
which are local to module--not process. So if client code
and J DLL both use the same CRT DLL, then it's OK.
But I doubt it, especially in Unix, where each application
tends to link libraries statically to avoid compatibility
issues.
To see it in action, in Visual Studio, create a solution
...
Under unix, malloc/free (as well as other address space
manipulation mechanisms, such as mmap) manage
per-process memory, not per-module memory.
FYI,
--
regards,
bill
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
