Paul Davis [EMAIL PROTECTED] wrote:

> > > what is any of this for in the first place?
> >
> >You mean why do we allos someone to define lt_dlmalloc, lt_dlrealloc,
> >and lt_dlfree? I don't know :)
>
> yes, thats precisely what i mean. what problem is this attempting to
> solve? some bizarre platform where ltdl.c can't call malloc()?

Personally I consider this to be a good thing for libraries.  It is useful
if you want to use a different (underlying) memory allocation API.
Imagine you want to pass part of a shared memory arena (IRIX uses such)
and libltdl.so tries to free() it with the standard libc call, this might 
fail and crash the program.  Also M$-Windows knows different
memory allocator APIs.

Cheers,
        [EMAIL PROTECTED]


_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool

Reply via email to