> But when the compiler builds the function it doesn't know whether the=20
> caller will be using function prototypes or not.

That is true if your frame of mind is the traditional C compilation /=20
linking system. But:

Embedded programs are very small compared to the memory of a PC. Hence=20
the compiler pass can do the front-end part of compilation (including=20
generating all traditional compiler error messages), delegating code=20
generation to the 'linking' pass.

These days C code without prototypes is bad, very bad. If you relay want=20
that ability in a compiler I would suggest a flag=20
-I-am-stupid-and-want-to-do-without-prototypes or something like that.=20
That gives 99% of the world an efficient compiler and 1% a fully=20
compliant one. (PS: about the same can be said for recursion and=20
function pointers. It required to be fully C compliant, but not often=20
needed in a small embedded system.)

--=20

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.