On 9 Sep 2015, at 21:45, Brad Roberts via dmd-internals wrote:
I'm very much in favor of seeing shared libraries become a reality, but there's a necessary process that's needed to ensure the required behavior: backwards abi compatibility. The major projects that ship shared libraries (ie, libgcc, libc, etc) have tooling (that I've never looked at) to detect breakage. This covers both no changes to existing symbols as well as controlled and acknowledged introduction of new symbols. Production quality shared library support is a big step up in responsibility.
Not really. Just increment the SOVERSION (or equivalent) on every single release. Then it won't be assumed to be backwards-compatible in the first place.
— David _______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
