[EMAIL PROTECTED] wrote:
But there are other operating systems using SQLite that do
not work this way. They need a way to initialize mutexes
(and possibly other objects such as malloc) prior to running
any SQLite interface. And the initialization needs to be able
to fail and return an error code.
This is true of the Porter layer that we use on our set-top boxes.
I had to add sqlite_initialize(...) and sqlite_finalize(...)
functions when I ported SQLite 2 to our Porter.
To accomodate this need, we are considering an incompatible
API change to SQLite. We are thinking of requiring that an
application invoke:
int sqlite3_initialize(...);
Sounds good to me. I would also recommend adding:
int sqlite3_finalize(...);
- Richard Klein
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
