Maybe we should explain the term 'wrapper'.
I'm using wrappers around the salite dll in my own code.
But a wrapper might be seen over here as additional library (dll or so)
others can use.
A redistribute part, which i don't like.
(Like the VB 'wrapper' dll)
----- Original Message -----
From: "Walter Meerschaert" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Thursday, August 25, 2005 3:43 AM
Subject: Re: [sqlite] Why can i open a textfile?
D. Richard Hipp wrote:
Most people who are using SQLite successfully have, I imagine, either
written their own wrappers around the core API (which
is not hard as I do provide you with a lot of helper routines
such as sqlite3_vmprintf and friends) or they are using an existing
wrapper written by someone else.
Indeed I wrote a thin wrapper when I started using SQLite 6 months ago. I
now retract my request for more control over the open function, as one of
the features of SQLite that I really liked was that it didn't have an
extensive set of "features". I can and will implement the read/only and
exclusive tests in my own open wrapper, and return or throw where
appropriate.
