Eco-C Compiler

[Chris Torek]

>>the parser barfs on "printf (...)" and not on "printf(...)".

>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.
>(Flames expected).

...and received: the problem was that the original wording was ambiguous.
The *intent* is that any identifier followed by a left parenthesis, with
nothing other than whitespace intervening, is a function call.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris at umcp-cs		ARPA:	chris at maryland