Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ssbell!weeks
From: weeks@ssbell.IMD.Sterling.COM (John Weeks)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Turbo C or MSC
Message-ID: <678@ssbell.IMD.Sterling.COM>
Date: 29 Mar 90 22:57:02 GMT
References: <26942@ut-emx.UUCP> <529@ohs.UUCP>
Organization: Sterling Software, FSG-IMD, Bellevue, NE.
Lines: 30

In article <529@ohs.UUCP> bhan@ohs.UUCP (Bruce Hansen) writes:
>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. :-)

Aren't we all! |:-) 

The answers to  your questions: very good and yes.  The integrated debugger
is very good - within its range of capabilities.  I find that I can find
most typos and simple logic errors, errors that are, as it were, internal to
the C language and my program.  When you try to trace/debug the interaction
of your program with the environment, I find myself wanting a little more
information, the kind you get with register displays and assembler dumps.
And this is where the stand alone debugger shines.  I'd say that your need
fror the stand alone debugger has more to do with the kinds of code you
are writing than with your current capabilities.  On the other hand, the
ability to *use* it depends on your capabilities and knowledge.  

I would note, though, that you don't have to be an assembler *programmer*
to make use of the information derived from register displays, assembler
dumps, etc.  You do have to aquire some knowledge about notation and about
e.g. intel architecture.  


-- 

John Weeks                                    Phone:  (402) 291-8300
Sterling Software FSG/IMD        e-mail: uunet!ssbell!weeks
1404 Ft. Crook Rd. South         e-mail: weeks@ssbell.IMD.Sterling.COM