The free() thing and function names

T. William Wells bill at twwells.com
Sun Sep 17 07:03:03 AEST 1989


In article <1989Sep15.183248.2955 at utzoo.uucp> henry at utzoo.uucp (Henry Spencer) writes:
: In article <841 at uniol.UUCP> lehners at 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 at twwells.com



More information about the Comp.lang.c mailing list