Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!hao!oddjob!gargoyle!ihnp4!cuae2!ltuxa!ttrdc!kad
From: kad@ttrdc.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: QuickC
Message-ID: <1909@ttrdc.UUCP>
Date: Tue, 22-Sep-87 11:22:08 EDT
Article-I.D.: ttrdc.1909
Posted: Tue Sep 22 11:22:08 1987
Date-Received: Fri, 25-Sep-87 06:36:38 EDT
References: <1485@killer.UUCP> <3320052@hpsrlc.HP.COM> <3826@watdcsu.waterloo.edu> <2347@i.cc.purdue.edu> <1569@killer.UUCP>
Reply-To: kad@ttrdc.UUCP (Keith Drescher)
Organization: AT&T Computer Systems Division,  Skokie, Ill.
Lines: 22

In article <1569@killer.UUCP> richardh@killer.UUCP (Richard Hargrove) writes:
>
>And I'm looking forward to CODEVIEW as soon as I get it in my MASM 5.0 upgrade.
>Then I'll use it with Turbo C.

How?
My copy of Turbo C does not provide any of the information that
codeview needs to perform symbolic debugging.  OK, TurboC will put
line numbers in the object file so you can do a combined source/assembly
listing, but as far as I can tell you can't access a variable by its
symbolic name because TurboC doesn't generate that information.

I hope that Borland does update their compiler eventually so that it 
places the CodeView information in the .obj file.  I like TurboC 
for the speed of compilation, and I like CodeView's debugging
abilities.  I just don't like waiting around for MSC to compile a
program.   Maybe QuickC will be the answer to my needs.
-- 
Keith Drescher (kad@ttrdc)          	   | ... You can check out any      
AT&T                                       | time you like - but you can
Computer Systems Division, Skokie, Il.     | never leave ...              
PATH: ...!ihnp4!ttrdc!kad                  |          - Hotel California