Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: C compilers..
Message-ID: <14184@smoke.BRL.MIL>
Date: 18 Oct 90 16:59:14 GMT
References: <3328@orbit.cts.com> <1990Oct17.181845.7369@nntp-server.caltech.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <1990Oct17.181845.7369@nntp-server.caltech.edu> toddpw@tybalt.caltech.edu (Todd P. Whitesel) writes:
>Come on, you're not being fair. ORCA/C will be a pretty decent compiler when
>they get the $!@#$ bugs out and finish making it ANSI compliant.

While it's usable as of release 1.1, so long as one is constantly aware
of the likelihood of genuine compiler bugs (as opposed to programmer
misexpectations), ByteWorks has essentially just one technical employee
(Mike Westerfield), and he tends to work primarily on one product at a
time.  Thus, until ORCA/M 2.0 and the next upgrade of ORCA/Pascal are
released, ORCA/C will very likely remain in the state that it is now in.