Am 07.09.2014 um 21:52 schrieb Simon Slavin <slav...@bigfraud.org>: > > On 7 Sep 2014, at 7:19pm, Richard Hipp <d...@sqlite.org> wrote: > >> mailingli...@skywind.eu> wrote: >> >>> Is it possible to change the fourth parameter in sqlite3_bind_XXX (and >>> probably other locations) because this seems to be for me the appropriate >>> type?! >> >> No. That would be a compatibility break. > > To supplement Richard's answer, I understand that this problem will be solved > in SQLite4, which can rely on size_t from the outset. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Can it also be solved in SQLite3 by overloading versions that support size_t as a parameter? As Roger pointed out ignoring the warning or implementing just a cast is insufficient. In case of an overloaded function the SQLite limits could also be handled correctly. Regards, Hartwig _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
