reserved names (was: Weird problem with C compiler under SCO)

[Doug Gwyn]

In article <597 at crdos1.crd.ge.COM> davidsen at crdos1.UUCP (bill davidsen) writes:
>What is not in the standard is any statement like "no future standard
>library calls will have external names which ...

Of course not.  There is no way that this Standard can constrain future
standards.  The best we can do is indicate intended "Future Directions"
as a guide to programmers and implementors concerning what to be wary of
even though it's specified a certain way by the current Standard.  But
it is not the intention that any follow-on C language standard usurp
more name space than we've already specifically set aside.