Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!decwrl!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.micro.pc,net.lang.c
Subject: Re: Eco-C Compiler
Message-ID: <1090@umcp-cs.UUCP>
Date: Sat, 3-Aug-85 23:25:17 EDT
Article-I.D.: umcp-cs.1090
Posted: Sat Aug  3 23:25:17 1985
Date-Received: Tue, 6-Aug-85 05:41:21 EDT
References: <436@bbnccv.UUCP> <401@que.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 13
Xref: linus net.micro.pc:4559 net.lang.c:5374

>>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@umcp-cs		ARPA:	chris@maryland