Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!cs.utexas.edu!texbell!nuchat!moray!urchin!p6.f506.n106.z1.fidonet.org!Bob.Stout
From: Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout)
Newsgroups: comp.lang.c++
Subject: Re: Zortech C++ compatability
Message-ID: <21983.26435922@urchin.fidonet.org>
Date: 5 May 90 18:13:38 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.6 - Fulcrum's Edge, Spring TX
Lines: 27

In a message of <May 04 16:49>, Peter DeVries writes:

 >><(3) any opinions on the debugging facilities.... e.g. how do they compare
 >><    with the Microsoft C debugger?
 >>It's better! :-) (You asked for an opinion!)
 >
 >Wait a second! Has anyone managed to debug a C++ program with the zortech
 >debugger that is any bigger than a TOY problem?

  Yes! how many lines are in your source files? Assuming reasonable modularity 
(a reasonable, though not always valid, presumption when discussing C++) the 
debugger should run OK - also assuming you read the manual and have set the 
switches so it has enough memory to work.

 >We have found that although the debugger is pretty neat, we are really 
 >stuck with Nothing at all once we try it on our real application.

  For truly mammoth applications, it's already been publicly announced (on 
BIX) that the 2.10 debugger will include variants to run with DOS extenders, in 
protected mode, and to do remote debugging. Since this much has already been 
leaked publibly, I can say as a beta tester that these do exist and seem to 
work as advertised. The bottom line is to compare the alternatives. CodeView 
is brain-dead (CV 3.0 which comes with MSC 6.0 is a little better, but not 
enough - mostly they just tacked on a new interface). Turbo Debugger is the 
state of the art, but the new ZDB has almost all the same features and works 
with ZTC++. In any case, programs that run out of memory with ZDB will also 
run out with TD (this is at least true with the new ZDB).