From: "AndrewJ" <luminous-is AT home DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <39792c34 AT pink DOT one DOT net DOT au> <Pine DOT GSO DOT 4 DOT 20 DOT 0007220018070 DOT 6739-100000 AT castor DOT cc DOT umanitoba DOT ca> <397a8065 AT pink DOT one DOT net DOT au>
Subject: Re: win32 tutorials?
Lines: 17
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <L5Ge5.208339$7o1.5337239@news2.rdc1.on.home.com>
Date: Sun, 23 Jul 2000 17:39:55 GMT
NNTP-Posting-Host: 24.42.120.18
X-Complaints-To: abuse AT home DOT net
X-Trace: news2.rdc1.on.home.com 964373995 24.42.120.18 (Sun, 23 Jul 2000 10:39:55 PDT)
NNTP-Posting-Date: Sun, 23 Jul 2000 10:39:55 PDT
Organization: @Home Network Canada
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


> so there would be no problems with a win 3.1 programming book?

Well, yes and  no.  Win16 was a 16-bit system.  Win32 is... ta da... 32-bits.
Many API functions were changed to use 32-bits, and some API calls were
removed/replaced in Win32.  The basic idea is unchanged, though.  Your program
starts, does its initializations, draws its main window and waits in a loop
receiving messages from the operating system about keyboard and mouse actions.

 If you have a high bandwidth connection (or a lot of patience), you could get
the Microsoft Platform SDK from MS's site.  It contains libraries, headers and
many example programs in source code format illustrating how to do just about
anything in Windows.

AndrewJ