Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!voder!kontron!optilink!cramer
From: cramer@optilink.UUCP (Clayton Cramer)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Aztec C?
Keywords: C compiler
Message-ID: <418@optilink.UUCP>
Date: 29 Aug 88 17:24:04 GMT
References: <20752@tut.cis.ohio-state.edu>
Organization: Optilink Corporation, Petaluma, CA
Lines: 22

In article <20752@tut.cis.ohio-state.edu>, holly@tut.cis.ohio-state.edu (Joe Hollingsworth) writes:
> 
> I need to port some C code from IBMPC to Apple II.
> The only C compiler that I've found for Apple II is by Manx Software
> Systems, called Aztec C.  Has anybody had experience with
> Manx Software systems and Aztec C?  Thanks for any comments.
> 
> Joe Hollingsworth  Computer and Information Science @ OSU

I've used the Aztec C compiler for the PC several years ago, and my
impression was not favorable.  The PC keyboard has a number of keys
that generate two characters (00 xx) for a key code.  Typically these
are arrows, function keys, etc.  When I read a keystroke with getchar,
it returned only one character -- the second one.  There was no way
to distinguish what I received from the normal ASCII character with
the same code.  It struck me as a problem of someone porting over the
getchar function to the PC hardware and not looking carefully enough
at the funny codes generated by that keyboard.  It was hard to get
much enthusiasm for trusting the rest of the compiler after such an
obvious screwup.

Clayton E. Cramer