Path: utzoo!attcan!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.std.c
Subject: Re: Naming
Message-ID: <5056@scolex.sco.COM>
Date: 5 Mar 90 04:14:57 GMT
References: <MCDANIEL.90Feb20172440@orenda.amara.uucp> <1990Feb23.184656.3110@siia.mv.com> <16021@haddock.ima.isc.com> <MCDANIEL.90Feb27103334@amara.amara.uucp> <5016@scolex.sco.COM> <16064@haddock.ima.isc.com>
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 17

In article <16064@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
>>In article <MCDANIEL.90Feb27103334@amara.amara.uucp> mcdaniel@amara.uucp (Tim McDaniel) writes:
>>>Are standard library names utterly and completely reserved, or can I
>>>fake it with #define, as in
>>>	#define malloc(bytes)	my_malloc(bytes, __FILE__, __LINE__)
>
>The #define itself is legal (provided you first #undef any old one), but...

Is it?  I was under the impression that the name 'malloc' was reserved
completely.

Or is it ok only because the define gets file scope (as opposed to external
linkage, that is)?
-- 
Sean Eric Fagan  | "Time has little to do with infinity and jelly donuts."
seanf@sco.COM    |    -- Thomas Magnum (Tom Selleck), _Magnum, P.I._
(408) 458-1422   | Any opinions expressed are my own, not my employers'.