Ralf Wildenhues asked: > Are we committing to a stable API and ABI now? No, it's still the responsibility of the distributor of a shared library package to ensure that its API is maintained (if the library uses libtool versioning).
For restricting the exported symbols, there's - the approach with #defines in config.h, - the lib-symbol-visibility module (works with gcc only). For keeping backward compatibility while changing the semantics of exported symbols, there's - the approach with #defines in the header file, - the lib-symbol-versions modules (works with ELF only). Bruno
