On 9/9/15 1:08 PM, Martin Nowak via dmd-internals wrote:
On 09/09/2015 09:45 PM, 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.

We just killed the idea to make shared libraries the default.
https://github.com/D-Programming-Language/dmd/pull/5044
I don't think a stable ABI is feasible anytime soon and w/o that shared
libraries are a PITA.
But I still want to ship shared libs with FBSD so that they can be used
optionally.

I know it's a terminology nitpick, but it outlines a typical pattern in communication w/in the D community. Very black and white thinking. The idea isn't killed, it's just deferred. And not building towards it is certainly going to defer it for a long time.
_______________________________________________
dmd-internals mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-internals

Reply via email to