-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[EMAIL PROTECTED] wrote:
| I was thinking the same thing earlier today.
| Perhaps sometime next week.
Another issue is checkin 3545 which disabled the loading of extensions.
~ The problem is that those of us building wrappers for other languages
have no way of telling what SQLITE_OMIT's were active when the library
was compiled. I currently just assume the defaults that SQLite ships
with, but now the default is different between 3.3.8 and 3.3.9. (ie
extension loading is present by default in 3.3.8 and not present by
default in 3.3.9). Asking users to supply the flags will be fairly hard
since they'll have to understand C compilation and the autogeneration of
these files. Even harder if they get the SQLite library via some other
mechanism (eg the dll downloads from the SQLite site itself).
A suggested solution is to have program with code like this:
#ifdef SQLITE_OMIT_CURSOR
~ printf("#define SQLITE_OMIT_CURSOR\n")
#endif
#ifdef SQLITE_OMIT_LOAD_EXTENSION
~ printf("#define SQLITE_OMIT_LOAD_EXTENSION\n")
#endif
As part of the "make install" process or something similar, run the
binary and insert the output into sqlite3.h. That way other code using
sqlite3.h will then know what functions are present in the
binary/library corresponding to the .h
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFj8lzmOOfHg372QQRArApAJ4xjSt+W5DGQm66AGczvt/zg3gQKQCfdzyk
tCXLwgD4r17KzAho7mAD69M=
=nVsX
-----END PGP SIGNATURE-----
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
