quote:
Originally posted by CookieRevised
Nope, there are sill many many errors. Some could be in the original file also, but most are caused by the auto-converting.
Stuff like:
var ADDRESS = ADDRESS64;
=> ADDRESS64 isn't defined as it was a structure
var ADDRESS_SIZE = sizeof(ADDRESS);
var ADDRESSINFO_SIZE = sizeof(ADDRESSINFO);
=> sizeof() is invalid in JScript and also these were structures
var AGENTAUDIOERROR_DEVICE = AGENTAUDIOERROR(1);
=> Arrays which aren't defined
var ALID_CHARSET = VALID_CHARSET = -27;
=> Dunno if this is due to the auto-converting or if this was already so in the original file. But it doesn't make much sense. Might need to check with the msdn library.
var AMF_AUTOMATICGAIN = -1#;
=> # isn't valid in JScript
var BEGIN_INTERFACE = virtual void a() {};
=> hmmmm....
var BFT_LOG = "\x01" | BFT_LOG_DIRECTORY;
=> Makes even less sense (boolean comparisson between a string and a number)
var CANNOT_LOAD = UINT(-8);
=> Dunno if this was in original file or not.
Also check every negative number. As I said earlier, a negative 'integer' isn't the same as the same number as a negative 'long'. eg: -1 as an integer (2bytes) is 65535 as a long (4bytes).
All these examples or only one example of the same kinds I got from quicky browsing the file, the file is full of things like these...
All of those were in the original file. My "auto converting" just didn't catch them.
Don't forget this was meant to be a quick reference to find the values of constants, not a file with entirely valid JScript. It was shawnz' idea to create a wrapper object, not mine.
Anyway, the latest is here:
http://m00.cx/win32api.txt
I would say, even though there are bound to be small errors, it's *useful* as a reference for Win32 API constants.
