🚀 go-pugleaf

In article <1991Feb15.224409.23871@aero.org> jordan@aero.org (Larry M. Jordan) writes:
[Deleted discussion of problems with stdlib.h and environ pointer]

>volatile keyword... My question:  What must I do?  Must I go in
>and "condition" any SDK header file so that it finally pleases the
>Zortech compiler, or do I use the Zortech supplied header file and
>change "environ" to reference the Zortech pointer to the environment
>(envptr)?  Or what?  How should things be configured?

I would not attempt to use the includes that appear in the windev\include
directory other than windows.h.  I would try to make Petzold's code work
with whatever Zortech is using as a pointer to the environment.  That will
work better than trying to kludge something of Microsoft's to work with
Zortech.

>This raises another question:  What if I want to use some of the
>Zortech libraries.  Can I along with the windows libraries?  What
>problems must I look out for?

I use ONLY Zortech's libraries (with the exception of libw obviously).
I had no end of troubles trying to make slibcew, etc work with Zortech
and then I found a file on Zortech's BBS (206)822-6907 called WIN3KIT.COM.
All it does is take your zl?.lib files and combine them with the libs
that came with the SDK to produce libraries that work excellently.  All I
typically link with is libw.lib, zlsw.lib, and pls.lib.  This way if you
link with a tool library you shouldn't have any problems.

John Munsch
Q: Why did Microsoft codename Basic for Windows Thunder?
A: Because they couldn't call it Lightning.