Xref: utzoo comp.lang.c++:1806 comp.lang.c:13428
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Debugging Zortech C++
Message-ID: <920@cps3xx.UUCP>
Date: 21 Oct 88 19:03:25 GMT
References: <1142@leah.Albany.Edu>
Organization: Engineering, Michigan State U., E. Lansing MI
Lines: 27

in article <1142@leah.Albany.Edu>, emb978@leah.Albany.Edu (Eric M. Boehm) says:
> Keywords: Zortech Codeview Unknown symbol
> Xref: cps3xx comp.lang.c++:1807 comp.lang.c:13214
> 
> I purchased Zortech C++ a few months ago. One of the reasons I purchased
> it (other than object oriented programming) was its "compatibility" with
> Codeview. However, a recent attempt at debugging was quite frustrating. I

Microsoft does not publish their specs on the stack frame for local 
variables. Therefore, anyone who makes a compiler that specifies that
it is Codeview compatible really means that you can step through code
and examine global variables with Codeview. I don't have my Zortech
manual here at work with me, but I believe I saw somewhere in the manual
that you cannot look at local variables. This really is not a Zortech
specific problem, it'll happen with anybody's compiler.

I like the ZOrtech compiler alot, however, their ads are a bit
misleading, as they state that you can compile any Turbo C or Microsoft
C code without changes and that it is Codeview compatible. The
memory manipulation commands are different between Turbo and Microsoft.
Zortech does it Microsoft's way. Also, ZOrtech's method of doing
interrupts is completely different than either one.


John H. Lawitzke      UUCP: ...rutgers!mailrus!frith!fciiho!jhl
Michigan Farm Bureau        ...decvax!purdue!mailrus!frith!fciiho!jhl
Insurance Group