Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!husc6!cmcl2!beta!myxm
From: myxm@beta.UUCP (Mike Mitchell)
Newsgroups: comp.os.minix
Subject: Re: Turbo C and Minix
Message-ID: <7035@beta.UUCP>
Date: Tue, 30-Jun-87 09:49:01 EDT
Article-I.D.: beta.7035
Posted: Tue Jun 30 09:49:01 1987
Date-Received: Sat, 4-Jul-87 22:57:51 EDT
References: <1716@marque.UUCP>
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 24
Summary: I'm working on this!

In article <1716@marque.UUCP>, doug@marque.UUCP (harris) writes:
> Having just received my Borland Turbo C (the T shirt is swell:-),
> be misunderstood :--).  In particular has anyone used Turbo C

The answer is yes, however, I am still having problems getting the 
kernel to link. I have successfully used the Turbo C to create and
maintain a Minix library of tiny/small memory model routines. When
I compile something using the tiny memory model, everything seems
to work fine. I am still having problems figuring out what the deal
is with the small memory model (separate I&D). But, from what I can
tell, the Turbo C compiler generates code which is much much smaller
than that from the Minix C compiler and a little smaller than the
code from the PC/IX C compiler.

Personally, I like the speed. I can compile something on an AT using
Microsoft C and on an XT with Turbo C--the funny thing is that they
both finish about the same time!

If you decide to persue the idea of Turbo C in a development environment,
please keep me informed! I am interested.

Mike Mitchell
myxm@lanl.arpa
{backbone sites}!cmcl2!lanl!myxm