Eco-C Compiler

[Walter Bright]

In article <401 at que.UUCP> chris at que.UUCP (Chris DeVoney) writes:
>John Lowery wrote about the Eco-C compiler in article <436 at bbnccv.UUCP).
>
>>     1.  It  is  true  that the parser barfs on "printf (...)" and not on
>> 	"printf(...)".  (note  the  space).
>
>You're right, he doesn't like it, but he need not accept it.
>K&R don't say it's ok to put a space between the function name and 
>parens, ANSI don't say it okay, and I just avoid the practice. Oh, well.

C is a tokenized language, and since 'printf' and '(' are separate
tokens, any amount of whitespace may appear between them. The only time
that whitespace has to be handled in the definition of the language is
in dealing with the preprocessor.