>>> additionally, the compiler's prototypes do not necessarily match
>>> the kernel's prototypes, and that may not be an error.
>> It is an error.
>> I understand that Technical Corrigendum 2, an official amendment to
>> the C standard, will state that all identifiers reserved by a hosted
>> implementation are also reserved for a freestanding implementation.
> Well, I don't have this standard, but what about malloc?

Read carefully.  malloc would be a reserved identifier.  Whether there
actually exists any routine by that name, and if so whether it has the
same semantics, is not specified (at least not by what the poster you
replied to posted, though by analogy to the str* and mem* functions one
could take it as saying it would have to either not exist or work the
same way).  But it mustn't be used as a name for "user" code.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu