On Fri, Jun 29, 2012 at 10:32 AM, Stephan Beal <sgb...@googlemail.com>wrote:
> On Fri, Jun 29, 2012 at 4:30 PM, Richard Hipp <d...@sqlite.org> wrote: > > > Maybe the thing to do is globally replace SQLITE_ with SQLITE4_? > > > > > That would be my preference, but it admittedly makes porting more > difficult, You think? You already need to do a global search/replace of "sqlite3_" to "sqlite4_". How much harder is it to do a separate search/replace of "SQLITE_" to "SQLITE4_"? > and i wouldn't cry too much if you decide to punt on this > problem. i'm working around it now to disable v3 support if v4 is enabled. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
