[Info-vax] Whither VMS?

[ChrisQ]

MetaEd wrote:

> 
> Here, let me Google that for you. ;-)
> 
> http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1336.pdf
> 
> See section 7.1.3. As I read it, a C library function identifier is a
> reserved word IFF the associated header file is included. No idea if
> this is enforced by any compilers. So, for example, you may define
> your own malloc() but you shall not also include <stdlib.h>. Also, as
> I read it, certain identifiers are reserved at all times, such as
> those beginning with double underscore.
> 
> Please note the cited document is a draft revision of the C99 standard.

Obviously, if you include a header with a function prototype, you would 
expect to be in trouble if you then try to redefine the function within 
the module. Any function becomes "reserved" if you have already declared 
a prototype in an included include file.

What this draft revision seems to be saying is that the function 
prototype is only recognised by the compiler as a *library* function if 
the associated header file is included. What this means is that the 
compiler development must closely track the standard lib development and 
changes, which makes no sense. That is, the compiler must be aware of 
all the standard lib functions and their formal parameters.

Tripe, if you ask me. (Tripe: popular at one time together with raw 
onions and malt vinegar. Very nutritious, so i'm told)

Regards,

Chris