4 ms·
Wait I thought C++ never even specified an ABI? Isn't name mangling and calling conventions left to the implementation?
by overgard 5y ago
Wait I thought C++ never even specified an ABI? Isn't name mangling and calling conventions left to the implementation?
- initplus 5y agoThere is a large culture among C++ users of distributing pre-compiled binaries of dependencies. See every Linux distribution, or the MSVC ecosystem where sharing precompiled .dll's is the norm. In this context ABI breaking changes are not viable due to the proliferation of pre-existing compiled binaries. What the standard says is only half the story...
- pjmlp 5y ago> There is a large culture among C++ users of distributing pre-compiled binaries of dependencies. See every Linux distribution, or the MSVC ecosystem where sharing precompiled .dll's is the norm. That is why I can code on the go in C++ on my travel netbook, while I mostly use Rust when plugged, or have to do a full build before leaving.
- jcelerier 5y agoSure, but in the end everyone codes against implementations, not the standard - the standard does not even know/care about dynamic libraries