On Fri, 2003-12-26 at 18:33, Bryce Harrington wrote:
Now, apparently AC_FUNC_MALLOC will redefine malloc to rpl_malloc if it determines malloc isn't "GNU compatible" ... which is probably a good reason not to use AC_FUNC_MALLOC. I'm not sure how that could possibly count as a feature.
Hmm, though isn't this what Autoconf is supposed to do? E.g., presumably there are non-GNU compilers that lack a proper malloc function so use this replacement.
For values of "proper malloc" where malloc(0) returns a valid pointer, I suppose. I have yet to find code that relies on that behavior (ours certainly doesn't).
AC_FUNC_MALLOC should more properly be called AC_FUNC_GNU_MALLOC, IMO.
Anyway, if we're building on a platform that doesn't even provide malloc() we probably have bigger problems to worry about.
-mental