Re: [sqlite] Bug: incorrect forward declaration ofsqlite3_win32_sleep

2012-06-19 Thread Roger Binns 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 18/06/12 22:55, Joe Mistachkin wrote:
 The new function is unsupported; however, it is required from places
 in the testing infrastructure where the sqlite3_sleep function cannot
 be called for one reason or another (e.g. there is no VFS yet).

In that case shouldn't it be inside #ifdef SQLITE_TEST which then means it
won't be encountered in regular builds so how it is declared is moot?

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk/gk48ACgkQmOOfHg372QQViwCg5Kbn3a8OEv82E7pOdWu70WPo
TPMAoJvTTguZ/JhBzpYw+PGhGohmBdVl
=4Rdl
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Bug: incorrect forward declaration ofsqlite3_win32_sleep

2012-06-18 Thread Joe Mistachkin 

Roger Binns wrote:

 The change looks okay on eyeballing it, but I do still question this
 symbol being exported SQLite API and undocumented.  There is already a
 sqlite3_sleep. 
 

The new function is unsupported; however, it is required from places in
the testing infrastructure where the sqlite3_sleep function cannot be
called for one reason or another (e.g. there is no VFS yet).

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users