On Tuesday, January 11, 2011 1:54 AM, Richard Hipp wrote: > This is, technically, a compatibility break.
But wasn't the original change also a compatibility break? But this time it may make it into the short-form software history at http://www.sqlite.org/changes.html? Having studied the changes made, first to 3.7.0 and then for 3.7.5, my opinion is that this could be a change for the better: whereas the original change to 3.7.0 may now be considered half-baked, the change proposed here actually makes quite a nice feature in some ways. And on Tuesday, January 11, 2011 3:11 AM, Tod Wulff wrote: > However for new dev efforts, does it not make sense to consider deploying > sqlite3_step_v2() which functions as the devs intend - i.e. leave > sqlite3_step() in place for the legacy code and made sqlite3_step_v2() the > new defacto standard for current/future dev efforts.?. I think this can be a good idea, but of course, people may just end up misusing it in the same way... Andy _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
