Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.lang.c
Subject: Re: The free() thing and function names
Message-ID: <1989Sep16.210303.9157@twwells.com>
Date: 16 Sep 89 21:03:03 GMT
References: <1989Sep14.022055.5961@twwells.com> <841@uniol.UUCP> <1989Sep15.183248.2955@utzoo.uucp>
Organization: None, Ft. Lauderdale, FL
Lines: 19

In article <1989Sep15.183248.2955@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
: In article <841@uniol.UUCP> lehners@uniol.UUCP (Joerg Lehners) writes:
: >What does the standard say about standardized function overriding ?
:
: The answer is a little complicated.  Assuming you just want to use a
: standard function's name for your own purposes, you can always do this
: provided (a) it doesn't begin with __ or _[A-Z], and (b) you do not
: #include the standard header declaring that function.  If either of these
: restrictions is violated, behavior is "undefined", i.e. it's up to your
: compiler and it's not portable.

The name must also not have external linkage. 4.1.2:

"All external identifiers declared in any of the headers are reserved,
whether or not the associated header is included."

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com