> On Dec 31, 2019, at 7:03 AM, Richard Damon <rich...@damon-family.org> wrote: > > 1) The C API between separate compilations is very well established, and > fully documented in most environments.
Agreed. APIs between library boundaries generally need to be C. This is pretty easy to do though (I've done it multiple times in my current job.) You just write some C wrappers for the public methods. > On Dec 31, 2019, at 7:19 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > 5) SQLite has to work on your set top box. On your Wifi base station. On > your Home hub. On the machine that runs the car park. All these things have > C compilers. Not all these things have C++ compilers. This may have been an issue ten years ago, but is it still? I did some R&D on embedded systems last year, and C++ support looked pretty ubiquitous. The heftier embedded boards run Linux, the middleweight ones have C++-friendly environments like mbedOS or ESP32-IDF, and even tiny 8-bit Arduino microcontrollers have an OO C++ API, even though they call it C to avoid scaring the newbies. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
