> 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] -----------------------------------------------------------------------------
