Alessandro Vesely:
> The language we are using is C, for the good and the bad of it.
> And I don't think that the time and space that __stdcall 
> might have globally saved at runtime will ever balance the 
> time and space devoted to discussing it.

Eli Zaretskii:
> Why did you need to use __stdcall?

At this stage: It will catch any callback into the CRT without having been
declared __cdecl. This is important since the Microsoft CRT are built with
__cdecl calling convention while in all other cases it is built with
__stdcall (WINAPI) calling convention. Some developers love to use the
__fastcall calling convention. If these callbacks are declared as __cdecl,
the code will be compatibel in either case.

JB



_______________________________________________
Make-w32 mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/make-w32

Reply via email to