🚀 go-pugleaf

	If I were you I wouldn't use Zortech C++ for much windows programming.
Contrary to popular belief (and the advertising) Zortech does not work with 
windows "straight out of the box".  You must modify windows.h in a very 
disturbing way. (Not the standard bit to prevent name mangling)  They define 
a couple of macros for you that are redefined in windows.h.  You must also 
download this thing called win3kit.com off their BBS.  It basically 
replaces a couple module in ?libcew and names the new libraries 
zl?w.lib.  Although knowlegable,  I found Zortech's technical support 
reluctant to procide any additional information.  It actually took be two 
calls to find out the above.  It would have been nice to have been told about
the problems with the libraries on the first call.  I still have a message 
with them that I need to be called back - so far no call.  I have since figured
out what was going on, but it's interesting to note that I never got a call
back.  With all fairness I have to make it known that I am a technical support
rep for mdbs, and I know that it can be a rough life.
	Zortech also requires the windows SDK.  Borland does not.  I was very
impressed with borlands product.  Borland actually includes the MS resource
compiler, and other MS tools.   
	One other problem with Zortech is that they didn't have inheirited
virtual function working untill version 2.18.

				Ted C.
				ee.ecn.purdue.edu!mdbs!ted

P.S.  Please forgive grammar and speeling errors.  It seems that english is
getting more and more like a second language.