It's a primitive form of namespaces in C. Renaming the function calls allows Sqlite2 and Sqlite3 to coexist within the same executable/binary.
Mind you, if the functionality of a documented function changes (as opposed to merely extended) I would think it would warrent a major revision number increase. Sqlite versions 3.1.0 and 3.2.0 did not change as radically as is planned for this upcoming release. --- Fred Williams <[EMAIL PROTECTED]> wrote: > Just curious, why is this being done anyway? I think this is the only > software product I have used that has this "feature." I fail to see the > usefulness from way up here above the source code, and I don't have time > to look deeper. But still curious as to why everybody has to rename all > their function calls between major releases. > > I'm on Delphi 7.0 and have never been forced to change anything because > of a new release, since Delphi 1.0. And closer to home, From PC DOS > Oracle to 8.0i Oracle. Seems like a lot of additional work, and would > like to understand why. > > Fred > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 03, 2005 7:56 AM > > To: sqlite-users@sqlite.org > > Subject: Re: [sqlite] Request for comment: Proposed SQLite API changes > > > > > > Joe Wilson <[EMAIL PROTECTED]> wrote: > > > > > > With the recent numeric/integer/division change, the working > > > check clause and this proposed API changed shouldn't the version > > > number should be bumped to 4.0.0 to indicate incompatibility with > > > past versions? > > > > > > > That would compel me to change *all* of the API to use a > > "sqlite4_" prefix instead of "sqlite3_". > > > > -- > > D. Richard Hipp <[EMAIL PROTECTED]> > > > > __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
