Hello Joe, Tuesday, October 30, 2007, 12:01:37 PM, you wrote:
JW> I think the proposed sqlite3_initialize() is a good idea and the JW> library might be a bit smaller/faster as well due to removal of JW> initialization checks in various functions. JW> Any concern about operating systems that already ship with a shared JW> sqlite3 library? Or is that what shared library version numbers JW> are for? JW> --- [EMAIL PROTECTED] wrote: JW> __________________________________________________ JW> Do You Yahoo!? JW> Tired of spam? Yahoo! Mail has the best spam protection around JW> http://mail.yahoo.com JW> ----------------------------------------------------------------------------- JW> To unsubscribe, send email to [EMAIL PROTECTED] JW> ----------------------------------------------------------------------------- You'll just end up exchanging an "are you initialized" flag for a "have you called the initialization routine" flag. I don't see it changing the size or complexity. Either way, SQLite either has to ensure it's initialized OR that someone has called the initialize function. It end up being the same check. I'm not sure why this is ever required. Static initialization flag that tells Sqlite to initialize itself internally or tells SQlite that the user has initialized it. C -- Best regards, Teg mailto:[EMAIL PROTECTED] ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
