Marcus wrote:
>> So, you might have a calling convencion issue... >> >> Just a guess, though. > > The sqlite3.h header has proper, "extern "C" {" wrappers around its > declarations, guarded by "#ifdef __cplusplus", so this is not an issue. > It is perfectly reasonable to call into the SQLite code from C++.Right, you can call sqlite from c++ - no problem. But here we define function pointers (compiled as c++), provide them via sqlite3_module structure to a c library. That is why I was guessing that it might not be clear for the c-library that the function pointer is compiled within a c++ frame.
Yes, that's a good point. (To the O.P.:) It would be a good idea to wrap the same 'extern "C" { }' around forward declarations for your functions that are going into that v-table (as pointers), and be sure that they are seen during compilation of those functions.
-- Larry Brasfield _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
