"Dimitrie O. Paun" dpaun@rogers.com writes:
ChangeLog Remove unused defines.
The idea is to have the same defines as Windows; even though we don't actually need them at this point we might want to someday.
On Thu, 7 Aug 2003, Alexandre Julliard wrote:
The idea is to have the same defines as Windows; even though we don't actually need them at this point we might want to someday.
Sorry, I don't quite understand: these defines are present only when compiling user32. Now, how do we know what defines MS uses to compile their user32? How can this ever be relevant to us?
"Dimitrie O. Paun" dimi@intelliware.ca wrote:
The idea is to have the same defines as Windows; even though we don't actually need them at this point we might want to someday.
Sorry, I don't quite understand: these defines are present only when compiling user32. Now, how do we know what defines MS uses to compile their user32? How can this ever be relevant to us?
We can use that kind of defines to do some optimizations internal to a dll: for instance make some exported by DLL APIs inline while building a dll. For user32 it might be all Rect APIs, some [G|S]etWindowLong APIs. For kernel32 it might me GetSystemDefaultLCID, GetSystemDefaultLangID, GetUserDefaultLCID, GetUserDefaultLangID, GetVersion.
etc.
"Dimitrie O. Paun" dimi@intelliware.ca writes:
Sorry, I don't quite understand: these defines are present only when compiling user32. Now, how do we know what defines MS uses to compile their user32? How can this ever be relevant to us?
We know because the defines are used in the Microsoft headers for the dllimport stuff. We don't need them for that purpose, but we could still use them for something else, like optimizations.