Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!dalcs!dalcsug!dalegass
From: dalegass@dalcsug.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Turbo C
Message-ID: <140@dalcsug.UUCP>
Date: Thu, 17-Sep-87 12:05:38 EDT
Article-I.D.: dalcsug.140
Posted: Thu Sep 17 12:05:38 1987
Date-Received: Sat, 19-Sep-87 08:58:34 EDT
Organization: Dalhousie University, Halifax, N.S., Canada
Lines: 20
Keywords: slow,large

Maybe I've just been incredibly spoiled by Aztec C, but I find Turbo C to
generate relatively larger and slower code (except for stdio, which Aztec C
kinda flops on).  I don't know why everybody is so crazy about it, except
possibly for the nice environment.

I've found very many cases of redundant instructions in the code that a very
minimal peephole optimizer would pick up, such as  MOV var,AX   MOV AX,var.

And where a simple MUL or DIV would suffice, there always seems to be a bunch
of pushes and calls.

I won't even mention the stack screwups it's generated, which caused major
crashes...

Overall, I'm not very impressed, although I do like the environment.
Hopefully Turbo C ver 2.0, or QuickC will offer good optimization with this
type of environment...


-dalegass@dalcsug.uucp