Any chance of publishing a modest but hardened "int sqlite3_numeric_buffer_type(const char*pBuffer,int length,int encoding)" API that extensions can use?
On Tue, Jan 23, 2018 at 4:43 PM, Richard Hipp <d...@sqlite.org> wrote: > On 1/23/18, petern <peter.nichvolo...@gmail.com> wrote: > > What is the fastest forward compatible way to gain use of the internal > > buffer value recognizers such as "SQLITE_PRIVATE int sqlite3AtoF()" in > > external C programs? > > > > There is no forwards-compatible way to do that. We reserve the right > to change the design and/or behavior of all internal interfaces at any > time and for any reason. And we do. Usually there are some internal > interface changes on every release. With a quick glance, I count 10 > separate, incompatble changes in the 3.22.0 release, with no telling > how many others I have overlooked. > > Furthermore, the internal interfaces are not hardened for general use > and are not general purpose. They will typically have quirks and > caveats and corner-cases that need to be avoided. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > 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
