Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!unmvax!ariel.unm.edu!nmsu!opus!ghenniga From: ghenniga@nmsu.edu (Gary Hennigan) Newsgroups: comp.os.msdos.programmer Subject: Re: CodeView and Quick C Message-ID: Date: 14 Nov 90 21:23:47 GMT References: <3079@lectroid.sw.stratus.com> <11607@hubcap.clemson.edu> <3082@lectroid.sw.stratus.com> Sender: news@NMSU.Edu Organization: NMSU Computer Science Lines: 46 In-reply-to: jmann@angmar.sw.stratus.com's message of 14 Nov 90 16:10:49 GMT In an article jmann@angmar.sw.stratus.com (Jim Mann) writes: >I prefer the Quick C interface to the Turbo C 2.0 interface. It supports >the mouse, editing is much easier, help is much easier and much more useful, >and you can compile, link, etc. easily. The integration of assembler into >2.5 seems much nicer than Turbo Assembler, which is strictly a command line >assembler. > >As for performance, I've seen QC/TC comparisons and the results are mixed. >QC produces faster code for some things, TC for others. I just got TC++ 1.0 and their IDE (Integrated Debugging Environment?) is extremely nice. It too provides mouse support and it has the ability to step or trace through your code with much the same features as the debugger, eg., watching variables, setting breakpoints, etc., without leaving the TC++ environment. It also gives you the option of going to Turbo Debugger for better control over debugging and mixed module programs. Also, using "projects", you can edit, compile, and link with other modules such as Turbo Assembler, and yes it has a windows-like environment so that multiple files can be edited, a file in each window with the ability to tile and so forth. Lastly, the "professional" products come with a profiler which, if you're going to try and squeeze as much as possible out of your code, is invaluable. I don't have any affiliation with Borland so I say this from a user's point of view, Borland always seems to be just one step ahead of MS in whatever they do. One good example of this is that their assembler doesn't have a lot of the bugs associated with MSASM and they have a set of simplified segement directives that make it much easier to interface assembler and C. The last thing that Borland gives you that is nice is that their debugger comes with a utility to allow you to convert CODEVIEW debugging info to theirs, so you can debug MS stuff with their product. Good thinking and marketing! Just my two cents, -- Gary Hennigan +---------------------------------------------------------------------------+ + e-mail: ghenniga@NMSU.Edu, henninsf@maxwel.NMSU.Edu + + Department of Electrical Engineering, Grad Student + + Physical Science Laboratory (ASS)istant systems programmer + +---------------------------------------------------------------------------+