Do the SmartSockets APIs use _stdcall on Windows?
Article ID: KB0084992
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
_stdcall: the standard calling convention for DLLs
_stdcall is the standard calling convention for DLLs under Win32. Using the standard calling convention confers the advantage that the functions in the DLL can be called from languages other than C, such as Visual Basic or PowerBuilder. ActiveX interfaces do solve this same problem, but only for ActiveX-enabled development environments.
SmartSockets 4.0 and previous versions used the _cdecl calling convention. SmartSockets now uses _stdcall to enable calls to SmartSockets DLLs from languages other than C and C++.
For backwards compatibility, you can continue to use the DLLs from the 4.0 release. Applications using SmartSockets 4.0 and 5.0 DLLs can coexist on the same machine.
_stdcall: the standard calling convention for DLLs
_stdcall is the standard calling convention for DLLs under Win32. Using the standard calling convention confers the advantage that the functions in the DLL can be called from languages other than C, such as Visual Basic or PowerBuilder. ActiveX interfaces do solve this same problem, but only for ActiveX-enabled development environments.
SmartSockets 4.0 and previous versions used the _cdecl calling convention. SmartSockets now uses _stdcall to enable calls to SmartSockets DLLs from languages other than C and C++.
For backwards compatibility, you can continue to use the DLLs from the 4.0 release. Applications using SmartSockets 4.0 and 5.0 DLLs can coexist on the same machine.
Issue/Introduction
Do the SmartSockets APIs use _stdcall on Windows?
Feedback
Yes
No
Powered by
