2014-08-29 5:22 GMT+02:00 Howard Kapustein <howard.kapust...@microsoft.com>:
> The Win32 DLL download includes a .def file, but comparing the exports with 
> the documentation's function page shows several inconsistencies
>
>
>
> doc but not .def
>
>   *   sqlite3_mutex_held
>   *   sqlite3_mutex_notheld

According to the documentation:
> The SQLite core only
> provides implementations for these routines when it is compiled
> with the SQLITE_DEBUG flag.


>   *   sqlite3_unlock_notify

This function is only available when compiled with
    -DSQLITE_ENABLE_UNLOCK_NOTIFY
So that's correct as well.

>   *   sqlite3_version (not a real API just a page name for the various 
> version functions/global so ignore)

Windows DLL's have some problem with exported data, and there
is a function sqlite3_libversion_number() which does the same.


> sqlite3_rtree_geometry_callback
> sqlite3_rtree_query_callback
>
> sqlite3_win32_is_nt

Those 3 are new in SQLite 3.8.6. I doubt the usefulness
of sqlite3_win32_is_nt(), because on current supported
systems this function should return 1 anyway. On
Windows RT it returns - surprisingly -  0 (which is
already fixed on trunk), so this function cannot
be thrusted anyway.   ....      ;-)

> sqlite3_win32_mbcs_to_utf8
> sqlite3_win32_set_directory
> sqlite3_win32_sleep
> sqlite3_win32_utf8_to_mbcs
> sqlite3_win32_write_debug

Those are all win32-specific. The only function that
might be interesting on some embedded
environments (read: Windows CE) is
sqlite3_win32_set_directory(). The other four
are not portable anyway, I don't see any
practical use for them.

Regards,
        Jan Nijtmans
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to