Yes. Good point. Before seeing Richard's last commits for pseudo-null pointer passing with static string type name, I proposed that the pseudo-null pointer API be extended with function signature forms which pass by value a user defined integer field for type information.
After further contemplation, I think it would be better to simply add the BLOB API function signature forms to pass optional user defined type information (by value) to achieve two factor pointer type identification. One can already test BLOB byte length. Adding an optional field to communicate explicit type id would truly rule out the possibility of dereferencing a nonsense BLOB which happens to be the same length in bytes as the expected host object. On Fri, Jul 21, 2017 at 9:03 AM, Gwendal Roué <gwendal.r...@gmail.com> wrote: > > > Le 21 juil. 2017 à 17:55, Gwendal Roué <gwendal.r...@gmail.com> a écrit > : > > > > First, this strcmp() give a lot of work to languages that wrap SQLite > and lack support for "static strings". Building a global \0-terminated > buffer that never gets deallocated is not always that easy :-) > > For the record, here is the commit that brings support for SQLite 3.20.0 : > https://github.com/groue/GRDB.swift/commit/0a603f1be3966d478b505373af95d2 > 57224ce5b0 <https://github.com/groue/GRDB.swift/commit/ > 0a603f1be3966d478b505373af95d257224ce5b0> > > The context is custom FTS5 tokenisers for Swift: > https://github.com/groue/GRDB.swift/blob/v1.2.2/ > Documentation/FTS5Tokenizers.md <https://github.com/groue/ > GRDB.swift/blob/v1.2.2/Documentation/FTS5Tokenizers.md> > > Gwendal > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
