Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!sac90286
From: sac90286@uxa.cso.uiuc.edu (Kubla Khan)
Newsgroups: comp.sys.atari.8bit
Subject: Re: Using CC8
Message-ID: <1989Sep7.143447.21789@ux1.cso.uiuc.edu>
Date: 7 Sep 89 14:34:47 GMT
References: <45266@bbn.COM>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: sac90286@uxa.cso.uiuc.edu (Kubla Khan)
Organization: University of Illinois at Urbana-Champaign
Lines: 21

In article <45266@bbn.COM> slackey@BBN.COM (Stan Lackey) writes:
>After using C quite a bit at work lately, I decided to try and use it
>on the 8bit.  I wrote a triv program and after several attempts gave
>up trying to get it to compile under cc8.  There is obviously something
>I'm missing.

Actually, it is CC8 that is missing something - that something is 
compatibility. I first learned C on a UNIX system, and later bought Turbo C.
The migration from UNIX C to Turbo C was nearly effortless, but when I later
tried a "Hello, world!" program under CC8, it took a LONG time to finally get
it working. Little things like replacing '{'s with '$('s weren't too difficult,
but the other incompatibilities are more painful. The real killer, however, is
the SPEED. After using Turbo C, CC8 seems to take forever. Then there's the 
linking process, which is also very slow. I guess I'm just spoiled by the
speed of Turbo C, but I find CC8 to be somewhat lacking as a development
environment.

Stick with assembler; it'll be easier on your nerves!

Scott
kubla@uiuc.edu