🚀 go-pugleaf

In article <1992Aug19.155648.6210@funet.fi> mn87504@cs.tut.fi (Naatula Mika) writes:
>I made my own Smalloc and and Sfree functions which call the standard
>malloc and free. I save in a table the allocated pointers and compare them
>before free is called. This is an easy way to catch many possible errors.

        For what it's worth, I got burned by getting internal errors in
malloc() and free(), then finding out that the reason for those errors was that
I was walking over memory that wasn't mine.  That experience made me a firm
believer in user-defined heap management, even if it is something as simple as
jacket routines (or macros) which control malloc and free.

        The fact that the C spec permits implementations to provide a malloc
that returns only NULL is another compelling reason for the programmer not to
rely on directly calling malloc or free.

        For portability and robustness, DON'T DIRECTLY USE malloc!


-- 
NOTE: I CAN'T SEND/RECEIVE E-MAIL HERE!!!  Use --> davisonj@ecn.purdue.edu <--
      During (roughly) August 20-25, I will be in transit.  Please be patient.
      The opinions and other information contained herein are not necessarily
      representative of Northern Telecom or any of its subsidiaries.