saitology9 <saitology9@gmail.com> wrote:
> On 8/23/2023 11:31 PM, Rich wrote:
>>
>> Given that sqlite ships as a built in part of Tcl (and has starting
>> with 8.6), calling a Tcl script only package that uses the built in sqlite
>> a "binary extension" is a stretch.
>>
>
> Well, sqlite is not loaded by default. To use it, you need to load it.
> So it fits the package or extension criterion. And it is binary. QED :-)

Yes, the sqlite extension is a binary extension.

But the fact that sqlite itself is a binary extension does not make the
www package itself a binary extension. Which is what it seemed your
earlier comments were implying, that www was a "binary extension"
because it used the built in sqlite extension.

On 23/08/2023 22:58, Schelte wrote:
> On 23/08/2023 23:35, Rich wrote:
>> So opening :memory: would seem to be safe (to the extent that someone
>> does not explicitly write code to go fish the 'cookie jar' db handle
>> out of the loaded module). Now, whether this is /documented/ behavior
>> or just a happy side effect I have not researched.
>
> It is documented behavior. https://www.sqlite.org/inmemorydb.html says:
> "Every :memory: database is distinct from every other. So, opening two
> database connections each with the filename ":memory:" will create two
> independent in-memory databases."
>
>
> Schelte.
>
Thank you. I hadn't realised that about SQLite. I am now even more
impressed by it.

PS Thank you everyone for your gentleness.