Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!iconsys.icon.com!ohs!bhan
From: bhan@ohs.UUCP (Bruce Hansen)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Turbo C or MSC
Message-ID: <529@ohs.UUCP>
Date: 28 Mar 90 17:26:27 GMT
References: <26942@ut-emx.UUCP>
Organization: Orem High School, Orem, Utah
Lines: 21

From article <26942@ut-emx.UUCP>, by boerner@ut-emx.UUCP (Brendan B. Boerner):
> In article <1990Mar26.174313.1976@eng.umd.edu> dank@eng.umd.edu (Daniel R. Kuespert) writes:
>>Both Quick C and Turbo C's integrated debuggers are toys,
>>more suitable for home use; with the Turbo C Professional package you get
>>Turbo Debugger, which is a considerable improvement on the Turbo C

This brings up the very dillema I have been struggling with the past couple
of weeks:  Is the integrated debugger "good enough"?  By "good enough," I
mean is it reasonbly easy to use and powerful enough for a programmer like
me who is not exactly up to the "professional" level of programming and
who does not know assembly anyway.  Based on this, I'd tell myself to just
get the regular package.  BUT, there is an excellent chance that I will
learn assembly in the next couple of years and that my own projects will
increase in complexity to warrant a purchase of Turbo C Professional.

To get to the point, the question is:  How good is the integrated debugger
and is it worth it to get Turbo C Professional?

Assume we're operating on a finite budget here. :-)

Bruce Hansen