Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!yale!sekora-jay
From: sekora-jay@CS.YALE.EDU (Jay Sekora)
Newsgroups: comp.sys.cbm
Subject: Re: C Compilers
Message-ID: <67333@yale-celray.yale.UUCP>
Date: 24 Jul 89 15:24:28 GMT
References: <808@orbit.UUCP>
Sender: root@yale.UUCP
Reply-To: sekora-jay@CS.YALE.EDU (Jay Sekora)
Organization: into systems, organs, and tissues.
Lines: 27

In article <808@orbit.UUCP> joe@pnet51.cts.com (Jim Henderson) writes:
>Abacus has a fairly good compiler called "Super C-128" which is 128 specific. 
>I've used the 64 version, and know somebody who has done mainframe development
>with it - no compatability problems; it's ANSI C!

do they have a new version out?  i have super-c 128, and it's pretty good,
but it's certainly NOT ansii c.  quibbles i have with it include:
	* stdio.h doesn't even try to be standard.  (e.g., getc returns
	  char, so you can't check its return value for EOF--this is one
	  of the smaller divergences.)
	* struct and union names conflict with other names, so common things
	  like struct name1 { blah, blah } name1 fail.
	* no real dynamic memory allocation.  there is an alloc function,
	  but if you want to free things you have to keep track of all the
	  size and position information yourself, and cross your fingers.
like i said, it's really pretty good, but the version i have is not standard
in any meaningful sense of the term, although the language itself (ignoring
libraries and system calls) is fairly close to first-edition C ("C Clas-
sic" :-) .  if they've come out with an ANSII version i'd be interested in
hearing about it.
-j.

____________________________________________________________________________
DISCLAIMER:  Everything I say is the|			sekora-jay@yale.UUCP
absolute and utter truth, but Yale  |		  {backbone}!yale!sekora-jay
doesn't necessarily know this.	    |		       sekjaya@yalevm.BITNET
				    | 6455 Yale Station, New Haven, CT 06520