Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!oracle!news
From: mfriedma@oracle.com (Michael Friedman)
Newsgroups: comp.std.c
Subject: Re: Naming
Message-ID: <1990Feb28.205601.6796@oracle.com>
Date: 28 Feb 90 20:56:01 GMT
References: <MCDANIEL.90Feb20172440@orenda.amara.uucp} <1990Feb23.184656.3110@siia.mv.com} <16021@haddock.ima.isc.com} <MCDANIEL.90Feb27103334@amara.amara.uucp} <12246@smoke.BRL.MIL} <MCDANIEL.90Feb28121657@amara.amara.uucp}
Reply-To: mfriedma@oracle.UUCP (Michael Friedman)
Organization: Oracle Corporation, Belmont, CA
Lines: 56

In article <MCDANIEL.90Feb28121657@amara.amara.uucp} mcdaniel@amara.uucp (Tim McDaniel) writes:
}gwyn@smoke.BRL.MIL (Doug Gwyn) writes:

}   You may #define your own malloc macro only if you don't #include <stdlib.h}.
}   ...
}   It would be better to use some name other than malloc for this macro.

}Let me be more clear about an intended application.  We'd like to have
}ANSI C library semantics available on all our development platforms.

You seem to be unnecessarily looking for trouble.

Why does your memory allocation routine have to be given the same name
as the ANSI C routine?

Why not use ANSImalloc in all of your code and just #define it to
malloc whenever you can?

}For instance, free given a NULL argument could just do nothing (if the
}platform's supplied free would abort in such a circumstance).  We also
}might like to have some sort of exception handling facility, or
}manually record a stack trace.
}
}In such a case, we'd just like to have a wrapper around the "real"
}function:
}    extern void * our_malloc(size_t);
}    #undef malloc
}    #define malloc(x) our_malloc(x)
}where our_malloc does wrapperish stuff and then calls the real malloc
}to do the real work.  We'd set up "our_stdlib.h" with such
}declarations.
}
}So, if we ever #include <stdlib.h}, even if I #undef malloc as a
}precaution, I can't #define a new malloc?  That's a bummer.  (Since
}we'll have an own_stdlib.h, there's a workaround, but it's still an
}annoyance.)
}
}I assume the reasoning is that the compiler might have, say, malloc()
}as a builtin, enabled upon seeing
}    #include <stdlib.h}
}However, it would have been easy to mandate that there be a way to
}turn it off, say via
}    #undef malloc
}after the #include.  Oh well, too late now.
}--
}Tim McDaniel
}Applied Dynamics International, Ann Arbor, MI
}Internet: mcdaniel%amara.uucp@mailgw.cc.umich.edu
}UUCP: {uunet,sharkey}!amara!mcdaniel


--
The passing of Marxism-Leninism first from China and then from the
Soviet Union will mean is death as a living ideology ... .  For while
there may be some isolated true believers left in places like Managua,
Pyongyang, or Cambridge, MA ...   - Francis Fukuyama