Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!mcnc!uvaarpa!murdoch!news
From: randall@Virginia.EDU (Ran Atkinson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Zortech 2.0 vs Turbo C++
Message-ID: <1991Jan23.182953.588@murdoch.acc.Virginia.EDU>
Date: 23 Jan 91 18:29:53 GMT
References: <1991Jan21.233029.29058@murdoch.acc.Virginia.EDU> <26419@uflorida.cis.ufl.EDU> <1991Jan23.130033.15755@informatik.uni-erlangen.de>
Sender: news@murdoch.acc.Virginia.EDU
Reply-To: Ran Atkinson <randall@Virginia.EDU>
Followup-To: comp.os.msdos.programmer
Distribution: comp
Organization: University of Virginia
Lines: 27

For those following the discussions about ZC++ and TC++ I need to make
a note of clarification.

Offline e-mail discussions with some other posters indicated that the
problems they were having with large projects involved situations where
they had full debug information turned on in each and every module of
the entire project.

My postings about not having seen any such problem with a large project
are accurate in so far as they go, but I never have full debug info
turned on for each and every module at any one time.  I have some modules
with full debug info turned on and others (most) with debug info turned 
off (which modules are turned on depends on what I'm trying to debug
and varies from time to time).

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 have no affiliation with either Borland or Zortech other than as an
ordinary customer and user.

Ran Atkinson
randall@Virginia.EDU