https://issues.dlang.org/show_bug.cgi?id=19760
--- Comment #19 from Jonathan Marler <[email protected]> --- >> 2. full static musl with ported malloc, stdio, personality, startup etc. >Won't work when mixing with C(++) code and you want a shared C runtime. Which >shouldn't be an extremely exotic use case (D plugin as DLL). You're straw manning. We're not talking about dropping support for msvcrt.dll, we're talking about making the default a static library. The developer can still opt-in to link against msvcrXX.dll, which they would when their software is going to be deployed with an installer or if they need to interoperate with C++ binaries. And by the way, DMD is currently only compatible with C++ programs that link against msvcr100.dll, a small subset of the versions of msvcrXX.dll. The fact that DMD binaries on windows are only compatible with a small subset of C++ binaries is a fact that should not be hidden from the developer. By making it "opt-in" rather than defaulting to one specific-version, you're making it easier for developers because now they know what their binaries are compatible with. > Anyway, I'm out of this discussion, I think I made my points. The main point I've gotten from you is that you think it's ok for simple programs compiled with DMD to not work on other's computers by default. Right now this is a fundamental disagreement between us that makes all your other points moot. --
