Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!hplabs!hpda!hpcupt1!kluft
From: kluft@hpcupt1.HP.COM (Ian Kluft)
Newsgroups: comp.sys.ibm.pc
Subject: Re: What about the Turbo C compiler?
Message-ID: <5930012@hpcupt1.HP.COM>
Date: 8 Aug 88 19:50:34 GMT
References: <371@gt-eedsp.UUCP>
Organization: HP Systems Technology Div, Cupertino CA
Lines: 26

cck@deneb.ucdavis.edu (Earl H. Kinmonth) writes:
> TurboC (1.0) has many bugs, some in fundamental areas. You say you want
> floating point arithmetic that works? What are you, some kind of
> communist?

I've heard that TC 1.0 was that bad.  I bought a copy of 1.5 shortly
after it became available.  I've had no problems with floating point or
any memory model.  Also, 1.5 has a VERY useful graphics library which
has saved me untold amounts of time (with bit-mapped fonts, Hercules/
CGA/EGA/VGA support, etc.)  I recommend that you upgrade to 1.5 to
resolve most or all of your complaints against TC.

The original message that led to this series of responses also asked about
low-level support and Unix semi-compatibility.  It seems to have good
coverage of the Unix library but MS-DOS is not Unix so there are plenty
of differences as well.

I like one feature of TC in particular - interrupt functions.  By putting
the keyword "interrupt" in a function definition, the compiler makes it
a function that can be called by a machine interrupt (i.e. it saves the
machine registers first and restores them before returning).

------------------------------------------------------------------
    Ian Kluft			RAS Lab
    UUCP: hplabs!hprasor!kluft	HP Systems Technology Division
    ARPA: kluft@hpda.hp.com	Cupertino, CA
------------------------------------------------------------------