Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!tektronix!uw-beaver!tikal!amc!jon
From: jon@amc.UUCP (Jon Mandrell)
Newsgroups: comp.os.cpm
Subject: Re: CP/M 80 C
Message-ID: <264@amc.UUCP>
Date: Wed, 3-Dec-86 14:25:08 EST
Article-I.D.: amc.264
Posted: Wed Dec  3 14:25:08 1986
Date-Received: Sun, 7-Dec-86 05:18:24 EST
References: <1211@brl-adm.ARPA>
Reply-To: jon@amc.UUCP (Jon Mandrell)
Organization: Applied Microsystems Corp.; Redmond, Wa.
Lines: 18

In article <1211@brl-adm.ARPA> lesh@BRL.ARPA (ISC | howard) writes:
>2)	the latest release of the Eco-C compiler is 3.47.  They too men-
>	tioned support for System V pre-processor directives.  The person
>	I talked to would not guarentee that a "bug" I was told was in
>	their CP/M 80 C compiler had been fixed.  (He says that K&R say
>	that there is supposed to be a space between the function name and
>	the left paran.)
>	(or at least that there is some scripture somewhere which justifies
>	their not making a change)

  I think this is backwards.  I use ECO-C (version 3.10) and you can NOT place
a space between the function call and the open paren.  K&R does NOT say that
a space is valid, but they never say that it isn't.
-- 
Jon Mandrell    (ihnp4!uw-beaver!tikal!amc!jon)
Applied Microsystems Corp.

"flames >& /dev/null" - me