Xref: utzoo comp.os.msdos.programmer:3642 comp.windows.ms.programmer:1062
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!seismo!uunet!pilchuck!dataio!fnx!nazgul!bright
From: bright@nazgul.UUCP (Walter Bright)
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer
Subject: Re: New Zortech C++/Windows 3.0 Developer...
Message-ID: <270@nazgul.UUCP>
Date: 25 Feb 91 18:34:21 GMT
References: <1991Feb15.041246.15904@murdoch.acc.Virginia.EDU> <24216@netcom.COM> <1991Feb15.224409.23871@aero.org>
Reply-To: bright@nazgul.UUCP (Walter Bright)
Distribution: usa
Organization: Zortech, Seattle
Lines: 28

In article <1991Feb15.224409.23871@aero.org> jordan@aero.org (Larry M. Jordan) writes:
/I am a new Windows 3.0 developer using Zortech C++.

In general, since you will be linking with the Microsoft libraries from the SDK,
you will need to use the .h files supplied by the SDK. Make sure those are found
in the include path before the Zortech ones.

Secondly, make sure the SDK libraries are in the command to LINK before the
Zortech libraries, and use the /NOE switch to LINK to make sure it accesses
the libraries in the right order.

The main problems to watch out for:
MSC and ZTC return floats and doubles using different mechanisms. Thus, avoid
trying to link together a module compiled with ZTC and one with MSC that
returns floats or doubles between them.
Some SDK sample code uses // comments in C code. This is not accepted by ZTC
(although it is accepted by ZTC++). // comments are not ANSI C.
Some SDK sample code uses incorrect prototypes, as in:
	void func(short i);
	void func(i)
	short i;
	{ ... }
These declarations are incompatible (the short is promoted to an int in the
second form due to ANSI C rules), the fix is to use the fully prototyped form:
	void func(short i)
	{ ... }

I hope this will get you started successfully.