|
|
Dmalloc Tutorial: 5.2 General Compatibility Concerns
5.2 General Compatibility Concerns
-
Realloc() backwards compatibility with being able to realloc from the
last freed block is not supported. The author is interested to
know who is using this (cough, cough) feature and for what reason.
-
Realloc() of a NULL pointer is supported in which case the library will
just make a call to malloc(). This can be disabled with the help of a
manual compilation option in the `conf.h' file.
-
Some systems allow free(0) to not be an error for some reason. Since 0
is not a valid address returned by the malloc call, it is debatable that
this should be allowed. See `conf.h' for some manual compilation
options to handle this.
-
Aside from possibly being slower than the system's memory allocation
functions, the library should be fully compatible with the standard
memory routines. If this is not the case, please bring this to
my attention.
This document was generated by Gray Watson on May, 16 2007 using texi2html 1.76.
This work is licensed by Gray Watson
under the Creative Commons
Attribution-Share Alike 3.0 License.
This page should be W3C Valid
XHTML and should work with most browsers.
|