_SQLite_Close problem

[argumentum]

...I know that I should leave the thread alone but clarification is always welcomed ( by me anyway ).

So there is the UDF ( that seem to me is been here since forever ), so it should not brake the old code and old code behavioral expectation.

To the casual user, the "-1" is cool. But if one is to use more than one DB, then the DB should be passed with the $hDB. And the user handles the handle returned by _SQLite_Open(). So is all good.

The proposed update/betterment, is worse, as the user is unlikely to use and/or understand FIFO, and if the user understands the concept, certainly knows that is better to control the handle to the DB that is in use, than a magic "-1" when more than one DB is used.

The internal array, is for internal dbg and help to the user. Internal use only.

So all in all, is better as is. Even as a teaching tool is better as is.
As is, you're kind of force you to pay attention to what you're putting down in the code.

PS: I like exploring ideas. I personally present a bunch. Some are adopted, and some are not ( mostly for good reasons  ).
My point is that presenting ideas for peer review is a good thing. At times they get a chance to see better. At times we get a chance to see better.  

[argumentum]

< my internet post twice for me, I look at it as an unwanted feature >

Edited June 17, 2020 by argumentum