cdecl vs. stdcall (APIENTRY) (d3d8.1 wrapper)

[Baker]

[mh]

[mh]

[Spike]

[Baker]

[Baker]

[mh]

[Spike]

PASCAL == pascal == stdcall. always. its termed stdcall because it works in pascal, c, VB, etc, and because its very hard to get a language developer to acknowledge other languages in their compiler. :P
The two are synonyms. Older code calls it pascal, newer code calls it stdcal. Different name, same meaning.

Regarding linking against winsock... Those functions are stdcall, on all platforms, be it 16bit or 32bit. All public winapi functions are stdcall. Otherwise it wouldn't be std, and couldn't be called from VB(6) and stuff. Point is, if the linkage WAS changed, then it wouldn't work even if it was statically linked.

A far call uses a different instruction to invoke and return, lcall vs regular call, lret vs regular ret (not to be confused with iret). These instructions push/pop the CS segment register as part of the call, and is basically a pain to use on any protected-mode system, although win3.1 was generally able to. You won't need to use it on any 32+bit system unless you're writing the operating system itself. On a 64bit system, it might be used to switch between 32bit and 64bit code, for instance.