Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!bronze!copper!rschmidt From: rschmidt@copper.ucs.indiana.edu (roy schmidt) Newsgroups: comp.os.msdos.programmer Subject: Re: TurboC 2.0 & TurboC++: Speed and Debugger Keywords: Object Orientecd Programming Message-ID: <1991Jan9.170423.24965@bronze.ucs.indiana.edu> Date: 9 Jan 91 17:04:23 GMT References: <1991Jan9.131031.21220@sbcs.sunysb.edu> Sender: news@bronze.ucs.indiana.edu (USENET News System) Distribution: na Organization: Indiana University, Bloomington Lines: 28 In article <1991Jan9.131031.21220@sbcs.sunysb.edu> kroe@sbcs.sunysb.edu (KiYun Roe) writes: > >While I'm at it, is there any significant difference between TD 1.0 and >TD 2.0 other than reverse execution? Does TD 2.0 continue to work well >from the keyboard without a mouse? > TD 2.0 works fine with and without the mouse. It has a much improved, context-sensitive menu system, so you don't need to plow through so many menus to get what you want. In some cases you can begin typing input, and TD will automatically open the input window you need! Of course, TD 2.0 is also smart for OOP, so you can debug TC++ and more recent TPascal programs using objects, classes, etc. Finally, TD 2.0 supports debugging TSRs and device drivers (!). I didn't do a runoff between the two compilers (TC 2.0 and TC++) for compilation speed. IMHO, I think this would splitting hairs. The more important points are adherence to ANSI C, library support, and code optimization. Saving even one minute in compile time is just not heart- stirring for me :-). -- -------------------------------------------------------------------------- Roy Schmidt | #include Indiana University | /* They are _my_ thoughts, and you can't Graduate School of Business | have them, so there! */