On 19 November, 2017 10:50, Joseph R. Justice <jayare...@gmail.com> asked:
>I'd think that dropping a newer version of SQLite, compiled as a run- >time linkable library, into a pre-existing binary compiled to use a >previous version of SQLite would require the ABI for SQLite (compiled >for use >as a linkable library) to be identical between versions, or >at least backwards compatible (such that a newer version of the >library can be used with an application compiled for a previous >version of the library to provide the same functionality as the >previous version, tho not newer functionality first provided by >the newer version of the library). >But is this a reasonable thing to expect on any platform, and >specifically on the Windows platform? >I don't know that it is, at least in this case. On Windows at least, unless deliberate action has been taken to ensure incompatibility (such as changing the definition of an exported function) or using "ordinal" rather than "name" exports, then the answer is yes. You can simply "replace" the DLL with a newer version. This is why programs that were written for windows in the mid-90's still continue to work to this day. The Win32 API has not changed since it was introduced many many many many many years ago, and there is no such thing as "Windows Version Obsolescence" except where it has been done deliberately and with pre-knowledge and malicious intent by the software author. The same applies for SQLite and anything else that has a stable interface. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
