On Tue, Jan 11, 2011 at 6:59 AM, Jean-Christophe Deschamps <j...@q-e-d.org>wrote:
> > My rationale is that either it's technically or economically feasible > for the offending applications' developpers to change their code to use > the library correctly (and that doesn't seem to be the case), OR very > simply avoid upgrading to the new SQLite versions. I don't get what > good reason they had to switch to new SQLite versions. > I don't think I explained the problem clearly. The proposed change is for the benefit of the applications customers, not the application developers. An end user (think: your mom) wants to upgrade her smartphone to the latest OS release. That new OS release includes the latest shared library for SQLite. But in so doing, some percentage of the apps she has downloaded cease to work. Sure, the problem really is that the apps were incorrectly coded. But does your mom really care about that? They worked before. Do we really want thousand, perhaps millions, of moms screaming that SQLite broke their phone when they upgraded? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
