Sherief N. Farouk <[EMAIL PROTECTED]> wrote: >> Have you actually tried it? Build a DLL with this code, check with >> Dependency Walker. These two functions get exported under the >> following names: >> >> [EMAIL PROTECTED] >> ?PI_TestEx@@[EMAIL PROTECTED] >> >> The first name is decorated, the second is mangled (there's a >> difference >> between these two things, but it doesn't matter in this context where >> all you want is to get an exported name exactly as it is in your >> code). >> >> Igor Tandetnik >> > > [Sherief N. Farouk] > > The decoration is due to the stdcall convention (APIENTRY). It's in > the form _FunctionName@<size_of_parameters>. If you don't want that, > use cdecl.
Well, yes, except that when you build a DLL to somebody else's specification, you are not free to choose which calling convention to use - you have to use one that the caller expects. On Windows, more often than not that means stdcall. Now, I don't actually know what calling convention SQLite expects a loadable extension to expose. If it's cdecl, then the OP should be all set with __declspec(dllexport). Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
