🚀 go-pugleaf

Chris Torek wrote:
> 
>         - Simply #include <stdlib.h>, and require that it be
>           correct (by fixing or replacing the implementation if
>           necessary).

Can't agree with that.  Changing system headers is a recipe for 
maintenance disasters.

> 
>         - Write my own module that implements memory allocation;
>           put any gross #ifdef'ing into it, and use `myalloc()'
>           everywhere.  This is particularly sensible if you want to
>           use a `void *' allocator (some of the systems return
>           `char *') and/or have a standard out-of-memory error.
> 
>         - Use a macro to define the name of the correct header, and
>           `#include MALLOC_H'.

No real objection to either of these.


Let me clear up one thing.  I was not saying that I agreed with the 
universal header concept, simply explaining what it was.  An earlier 
poster appeared to have misunderstood.

My preferred method is to encapsulate particular subsystems where 
portability is an issue.  I have been known to use a "sysdefs.h" or 
similar where system specific macros were defined, such as the
#define MALLOC_H <stdlib.h> from your example.


-- 
#####################################################################
Michael Smith                                       msmith@mpx.com.au
Emmenjay Consulting                 http://www.hutch.com.au/~emmenjay
#####################################################################