Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dataio.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!qantel!hplabs!tektronix!uw-beaver!uw-june!entropy!dataio!bright
From: bright@dataio.UUCP (Walter Bright)
Newsgroups: net.micro.pc,net.lang.c
Subject: Re: Eco-C Compiler
Message-ID: <744@dataio.UUCP>
Date: Sat, 3-Aug-85 10:15:18 EDT
Article-I.D.: dataio.744
Posted: Sat Aug  3 10:15:18 1985
Date-Received: Tue, 6-Aug-85 08:33:26 EDT
Reply-To: bright@dataio.UUCP (Walter Bright)
Organization: Data I/O Corp., Redmond WA
Lines: 14
Xref: watmath net.micro.pc:4831 net.lang.c:5911

In article <401@que.UUCP> chris@que.UUCP (Chris DeVoney) writes:
>John Lowery wrote about the Eco-C compiler in article <436@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.