Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ihlpm!leder
From: leder@ihlpm.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: TURBO C
Message-ID: <1148@ihlpm.ATT.COM>
Date: Thu, 28-May-87 16:50:39 EDT
Article-I.D.: ihlpm.1148
Posted: Thu May 28 16:50:39 1987
Date-Received: Sat, 30-May-87 04:55:49 EDT
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 31
Keywords: its here!!!!!!!

TURBO C IS ALIVE AND WELL!

By now, I am sure that most of you have plunked down your 69.95
(at Egghead in Chicago) or whatever demands your vendor has made to get
TURBO C.  If you have not, then you must because it is the fastest
compiler on the market.  It is as fast as BDS C (for those who remember
CP/M) and it is nice.  The only complaint that I have is that I have not
been able to find a way to set the stack size.

The exemod utility from the MSC 4.0 package reports that the requested
stack is 128 bytes.  Increasing this, using exemod helps some, but not
enough for the particular program I wanted to run.  I'm sure that the 
answer is just around the corner.

I have now ported 3 fairly large programs with minimal effort with the
exception of the stack problem.

For those people who don't want to use the integrated environment, the
same functuallity is available via command line commands for the compiler,
linker, and a make utility.

According to the documentation, the MS linker can read turbo .obj's but
because of undocumented record types, they cannot interpret the MS .obj's.

With one program that is a ~39K exe with MSC, it came out to ~35k with
turbo C.  The MSC options for program size reduction seem to make the
program larger.

If others want to send info (bugs, etc.) I will summarize on the net.

Bob Leder