Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utcsri!utegc!utai!garfield!dalcs!aucs!peter
From: peter@aucs.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Converting Microsoft C to TurboC
Message-ID: <386@aucs.UUCP>
Date: Thu, 25-Jun-87 08:31:40 EDT
Article-I.D.: aucs.386
Posted: Thu Jun 25 08:31:40 1987
Date-Received: Fri, 26-Jun-87 05:58:50 EDT
Reply-To: peter@aucs.UUCP (Peter Steele)
Distribution: na
Organization: School of Computer Science, Acadia Univ., Nova Scotia
Lines: 36

To continue...

>compilers are like religion ...

Apparently so. In my original posting on this subject, I certainly
didn't mean to upset anyone who uses and likes Microsoft C. After all,
I did say Microsoft C was good. But I also said it was slow. My
experiences so far with Turbo C have been very satisfactory and
as far as CodeView is concerned, when I first started using MicroSoft
C, I tried out CodeView, thought it was cute but mostly useless for
large applications, and have never used it again. I tend to program
in a modular way, adding small pieces of code at a time. Before I compile,
I visually inspect the code VERY carefully (I think this is a result
of being an assembly programmer in my early years), and then testing
it. If it doesn't work, I visually inspect the code again and quite
often find the bug. If I don't, I add some appropriate printf statements
and tried another recompilation and execution, and I usually find the
problem during this iteration (although not always). That is why I like
TurboC--it compiles so quickly it allows me to make several iterations
like this in very little time. I find this technique of debugging much
more effective than using a limited tool like CodeView. But these are
only my opinions, not a personal attack on anyone who uses and likes
CodeView. So PLEASE, keep your hackles down...

BTW, have you seen the ads for Microsoft QuickC/C 5.0? Sounds like
a good competitor for TurboC...


Peter W. Steele     UUCP     : {seismo|watmath|utai|garfield}!dalcs!aucs!Peter
Acadia University   BITNET   : {Peter|pws}@Acadia
Wolfville, N.S.     Internet : {Peter|pws}%Acadia.BITNET@WISCVM.WISC.EDU
Canada  B0P 1X0     PHONEnet : (902) 542-2201x121

PS: I found a bug in TurboC's memchr routine. It failed for me in one
instance where it should have found the byte I was looking for. Has
anyone come across a similar problem?