Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekred!kit!waynet
From: waynet@kit.CNA.TEK.COM (Wayne Turner)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Zortech 2.0 vs Turbo C++
Message-ID: <6901@tekred.CNA.TEK.COM>
Date: 24 Jan 91 15:59:36 GMT
References: <1991Jan21.233029.29058@murdoch.acc.Virginia.EDU> <26419@uflorida.cis.ufl.EDU> <1991Jan23.130033.15755@informatik.uni-erlangen.de> <1991Jan23.182953.588@murdoch.acc.Virginia.EDU>
Sender: news@tekred.CNA.TEK.COM
Reply-To: waynet@kit.CNA.TEK.COM (Wayne Turner)
Distribution: comp
Organization: Tektronix, Inc., Redmond, Oregon
Lines: 27

In article <1991Jan23.182953.588@murdoch.acc.Virginia.EDU> Ran Atkinson <randall@Virginia.EDU> writes:
>For those following the discussions about ZC++ and TC++ I need to make
>a note of clarification.
>...
>
>If you have problems with TC++ and a large project, you probably do not
>want to have full debug information for each and every module turned on
>at the same time.  This strikes me as a reasonable workaround, but if
>ZC++ _can_ handle everything in full debug at once (as I'm told --
>I haven't tried that yet because it slows down the debugger) then this
>might be a reason to prefer ZC++ to TC++.
>

I am working on a project that links in 70 OBJS, all with compiled
with debug info.  Total lines of source code is about 6000.  Load
image size about 270K.  Version 2.10 of Zortech debugger (zdb286) routinely
crashed when all modules contained debug info but version 2.10C
has worked OK so far. 

>I have no affiliation with either Borland or Zortech other than as an
>ordinary customer and user.

Likewise for me.
Wayne Turner
Tektronix, Inc.
Redmond, Oregon
waynet@kit.CNA.TEK.COM