Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!rutgers!att!poseidon!psrc
From: psrc@poseidon.ATT.COM (Paul S. R. Chisholm)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0
Summary: Turbo Debugger vs. Turbo C debugger; TC "Keyboard hot keys" available
Message-ID: <540@poseidon.ATT.COM>
Date: 19 Oct 88 17:24:21 GMT
References: <182@imspw6.UUCP>
Organization: AT&T Bell Laboratories
Lines: 27

<"He seemed like such a nice man . . . and then he turned out to be a writer!">

In article <182@imspw6.UUCP>, bob@imspw6.UUCP (Bob Burch) writes:
> From Ted Holden at HTE:
(Some screen dumps were included here, which would have been prettier
if the line drawing characters, which had their eighth bits stripped,
had been replaced by '|' and '-' as appropriate.)

> As you can see, the normal built-in debug features which come with Turbo C
> 2.0 are pretty serious.  The stand-alone debugger is for 386 style debugging,
> 486 style debugging, debugging with a second screen, debugging all kinds of
> exotic equipment, exotic screens, cathedral organs running DOS, etc.  Most
> people probably won't ever use it, but, then, you never know.

(Gee, I can't find TD486.EXE on my disk.-)  There are two other big
advantages:  TD leaves more room for the program to run in than TC.
And TD lets you have multiple "views" of the program (stack backtrace,
registers, source code with current statement shown, values of
expressions, etc.) in overlapping windows.  Of course, you get TASM, too.
  
> A quick template of function-key use (which is not provided and possibly
> should be)

Is available by hitting F1 F1, then selecting "Keyboard hot keys".

Paul S. R. Chisholm, psrc@poseidon.att.com (formerly psc@lznv.att.com)
AT&T Bell Laboratories, att!poseidon!psrc, AT&T Mail !psrchisholm
I'm not speaking for the company, I'm just speaking my mind.