[sqlite] Re: Cursor naming conflict

[Jeff Edwards]

We agree with you with the scenario that you build the sqlite library 
and then link it into a project, however in our scenario, which does 
not appear to be obscure, we take the entire sqlite source code and 
directly compile it into our project.  Under this scenario, the 
internal headers are visible and do create conflicts.

Just to reiterate, we are using OSX, not OS9.  The problem appeared in 
both xcode and code warrior, and x code is not an obscure development 
framework.


No
The "Cursor" object in SQLite is an internal name.  It does not appear
anywhere in "sqlite.h" or "sqlite3.h".  Since the neither XCode nor 
Carbon
are required to compile SQLite, the definition of Cursor should not 
appear
in any of the files included by SQLite either.  So there should be no
conflicts.  If you are getting conflicts, I think the blame belongs to
the build environment, not SQLite.  I think it ill-advised to go around
altering names in SQLite in order to work around problems in obscure
build environments such as Code Warrior for Mac OS 9.