On Sunday, January 21, 2007, 11:03:32 AM, Florian Weimer<sqlite-users@sqlite.org> wrote: >> Having SQLITE_TRANSIENT point to a real function is perhaps a >> good idea. The problem is such a change would break backwards >> compatibility of the API. Somebody who compiled against an >> older SQLite and who drops in a newer DLL with this change will >> find that their code no longer works. This is something we work >> very hard to avoid.
> You could redefine SQLITE_TRANSIENT and still check for the older -1 > value in the SQLite code (where you've got better control what the > compiler does). > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- I don't know if this is the right place to post suggestions to the SQLite developers, but why don't you do something like #define SQLITE_COMPAT_MODE and do these things like making SQLITE_TRANSIENT point to real function under #ifndef SQLITE_COMPAT_MODE? So the older users can compile under SQLITE_COMPAT_MODE and avoid having problems, while newly written code can rely on proper, clean code? ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
