Re: [sqlite] SQLite 3.20.0 postponed

2017-07-22 Thread Gwendal Roué
> Le 22 juil. 2017 à 08:14, Gwendal Roué a écrit : > > Still, I feel that static strings are a weird way to define keys. For > example, value subtypes in SQLite have the same requirement of needing > "unique subtype identifiers", and those subtypes are, today, ints.

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-22 Thread Gwendal Roué
> Le 21 juil. 2017 à 18:50, Richard Hipp a écrit : > > On 7/21/17, Gwendal Roué wrote: >> >> First, this strcmp() give a lot of work to languages that wrap SQLite and >> lack support for "static strings". > > But sqlite3_result_pointer() and

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread petern
, 21 July, 2017 14:49 > >To: SQLite mailing list > >Subject: Re: [sqlite] SQLite 3.20.0 postponed > > > >Indeed. Or Type(T) of long, or sqlite_int64, or whatever is most > >universal > >where porting other architectures is concerned. It would be a shame > &g

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Keith Medcalf
>To: SQLite mailing list >Subject: Re: [sqlite] SQLite 3.20.0 postponed > >Indeed. Or Type(T) of long, or sqlite_int64, or whatever is most >universal >where porting other architectures is concerned. It would be a shame >if the >API had to be changed later because the integer t

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Richard Hipp
On 7/21/17, petern wrote: > > How was adding to the BLOB API ruled out? It uses extra memory and CPU cycles, even on the vast majority of applications that do not use it. -- D. Richard Hipp d...@sqlite.org ___

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread petern
Indeed. Or Type(T) of long, or sqlite_int64, or whatever is most universal where porting other architectures is concerned. It would be a shame if the API had to be changed later because the integer type chosen couldn't hold a pointer. From there, in a closed compiled host C/C++ setting with the

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Keith Medcalf
On Friday, 21 July, 2017 10:51, Richard Hipp wrote: > But sqlite3_result_pointer() and sqlite3_bind_pointer() are not > invoked from those languages. The _pointer() routines are invoked > from C, and C does easily support string literals that are static > strings. > A

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread petern
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

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Richard Hipp
On 7/21/17, Gwendal Roué wrote: > > First, this strcmp() give a lot of work to languages that wrap SQLite and > lack support for "static strings". But sqlite3_result_pointer() and sqlite3_bind_pointer() are not invoked from those languages. The _pointer() routines are

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Gwendal Roué
> Le 21 juil. 2017 à 17:55, Gwendal Roué 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

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-21 Thread Gwendal Roué
> Le 17 juil. 2017 à 20:54, Richard Hipp a écrit : > > The 3.20.0 release will be delayed. Some concerns came up over the > new sqlite3_value_pointer() interface. Interface chagnes were made > over the weekend. But there are still concerns. So the decision has > been made

Re: [sqlite] SQLite 3.20.0 postponed

2017-07-19 Thread petern
Richard. Here is food for thought. Below is a contrived but realistic example of an embedded application wire format which demonstrates some expected extension function pointer allocations and another recent topic. SELECT DoTrackingRecalibrate(column1,CommandPacket(column2,column3)) FROM