On Mon, Jan 10, 2011 at 8:52 PM, Chris Peachment <ch...@ononbb.com> wrote:
> On Mon, 2011-01-10 at 19:54 -0500, Richard Hipp wrote: > > <snip> > > > This is, technically, a compatibility break. On the other hand, there > > appear to be vast numbers of smartphone applications that currently > depend > > on undefined behavior and will suddenly stop working if we don't make > this > > change. > > > > What's wrong with using a new function: sqlite3_step_v2() > The legacy applications we are trying to fix all link against sqlite3_step(). If we were to make them changes to sqlite3_step_v2(), we might as well just ask them to fix their code. But, as noted in the original post, that is impractical due to the large number of broken legacy applications. > > > _______________________________________________ > 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
