Article-I.D.: brl-adm.1211
Posted: Tue Dec  2 09:08:41 1986
Date-Received: Tue, 2-Dec-86 20:00:08 EST
Sender: news@brl-adm.ARPA
Lines: 24


	Thanks to all for responses to my query.

	I thought I'd pass on the results of phone conversations with two
CP/M 80 C compiler vendors.

1)	the latest release of Aztec C is 1.06d.  According to the vendor,
	it is System V compatible with respect to all the pre-processor
	directives (I didn't ask whether they had bit-fields yet).

	(The pre-processor stuff is important if you like Fred Fish's 
	DBUG program posted on the network a little while ago.)

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)

	Thanks again for your replies.  We still have not made any commit-
ments so any additional information will be appreciated.

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