NNAME1 u1
-#define DUMMYUNIONNAME2 u2
-#define DUMMYUNIONNAME3 u3
-#define DUMMYUNIONNAME4 u4
-#define DUMMYUNIONNAME5 u5
-#define DUMMYUNIONNAME6 u6
-#define DUMMYUNIONNAME7 u7
-#define DUMMYUNIONNAME8 u8
-#endif /* !defined(NONAMELESSUNION) */
-
-/* Calling conventions definitions */
Francois Gouget wrote:
On Wed, 13 Dec 2000, David Elliott wrote:
In order to allow __cdecl and __stdcall to be defined correctly without
including Windows headers it is necessary to split their definition out into
a new include file. This include file is then included into windef.h in
On Wed, 13 Dec 2000, David Elliott wrote:
[...]
At the very
least the C headers themselves need __cdecl defined correctly so it definitely
makes sense to seperate that out.
I'm not sure about that actually. '__cdecl' is the default C calling
convention so you should not need to specify it.
David Elliott [EMAIL PROTECTED] writes:
You should definitely revive it IMHO. Alexandre has said himself that it is
inappropriate for C library headers to #include windef.h. The most reasonable
way to do this is to seperate all of the Windows compiler definitions into a new
include file or
Alexandre Julliard wrote:
David Elliott [EMAIL PROTECTED] writes:
You should definitely revive it IMHO. Alexandre has said himself that it is
inappropriate for C library headers to #include windef.h. The most reasonable
way to do this is to seperate all of the Windows compiler