I think that sqlite3_initialize should be allowed to be called more
than once.
With the help of a static flag, only the first time it is executed
the proper initialize functions will be invoked, successive calls to
the sqlite3_initialize should just be a NOP operation...
---
Marco Bambini
http://www.sqlabs.net
http://www.sqlabs.net/blog/
http://www.sqlabs.net/realsqlserver/
On Oct 30, 2007, at 5:14 PM, Roger Binns wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[EMAIL PROTECTED] wrote:
It is also an error to
invoke sqlite3_initialize() more than once.
That is a pretty nasty restriction to have. If you link multiple
other
libraries into your program, each of which also uses SQLite then you'd
somehow have to arrange that only one of them calls sqlite3_initialize
which is a serious pain.
(The wxPython gui library used to have a similar issue when
initializing
things like cursors and colours and caused endless grief before it was
fixed to allow multiple calls).
In any event this is a very serious API change and really does qualify
for calling it SQLite 4.
Alternatively, you don't actually need the interface for 99.99% of
users
out there (Windows, Linux, Mac) so you could make it unnecessary for
them, but do require it for the various esoteric embedded systems.
That
would justify still calling it SQLite version 3.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHJ1hXmOOfHg372QQRAjCHAKCdH4R/OQNY3ALUli9nRCmbFeyDfACeIHcY
7irdFT/ofCgoNK0jERTjze8=
=yB1W
-----END PGP SIGNATURE-----
----------------------------------------------------------------------
-------
To unsubscribe, send email to [EMAIL PROTECTED]
----------------------------------------------------------------------
-------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
