Yet another effort at translating the Win32 API headers
Stewart Gordon
smjg_1998 at yahoo.com
Fri Mar 31 10:53:11 PST 2006
Comparing the #ifs in MinGW with the information on the MSDN website,
there seem to be a lot of errors! But I guess that we can identify
these combinations in what supports a given entity:
- 95, NT4
- 98, NT4
- ME, NT4
- NT4
- 98, 2000
- ME, 2000
- 2000
- XP
- Server 2003
There's also a lone mysterious _WIN32_WINNT >= 0x510 for a function not
documented on MSDN. I'd think it was preparing for Windows Vista,
except that
- Vista is internally numbered as 6.0
- there's no doubt going to be more than one new function in it
- Vista will have a whole new API anyway
I'm inclined that there are the following versions for the end
programmer to concern him/herself with:
- for Windows 9x compatibility: Windows98, WindowsME, WindowsNTonly
- for Windows NT compatibility: Windows2000, WindowsXP, Windows2003
- for IE compatibility: IE3, IE4, IE401, IE5, IE501, IE6
which should be mapped to internal versions based on the above list.
The only problem is that, since there's no way at the moment to import
version manipulation, we'd need to either maintain a copy of the mapping
code in each module that uses these versions, or use command line files
to set these versions. What do people think?
Stewart.
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS-
PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y
------END GEEK CODE BLOCK------
My e-mail is valid but not my primary mailbox. Please keep replies on
the 'group where everyone may benefit.
More information about the Digitalmars-d-announce
mailing list