2 ms·
Dynamic linking is there, yes. But the only globally shared libraries tend to be the OS ones - everything else, even the CRT (before it also became part of the
by int_19h 5y ago
Dynamic linking is there, yes. But the only globally shared libraries tend to be the OS ones - everything else, even the CRT (before it also became part of the OS), is normally installed side by side with the .exe, and every app has its own copy. Thus C++ ABI compatibility was not really an issue, except when you had to use closed-source C++ libraries.
Yes, the other big difference is that every DLL has its own namespace, so you can actually load two CRTs into the same process just fine - so long as you don't pass pointers/handles from one runtime to the other. But this kind of multi-runtime arrangement doesn't happen often in practice, except in plugin/extension scenarios (where different extensions might bring in different runtimes into the same process).
- pjmlp 5y agoCOM libraries aren't usually side by side, and they are used a lot. Even if they aren't installed on System32 (thankfully), they get their own slot under Programs. Most applications that do xcopy installs tend to be .NET based.
- int_19h 5y agoThese days, most COM libraries that aren't OS APIs are also installed side by side with the app, with information necessary for activation provided in .manifest - this feature has existed since WinXP. Although I would also say that third-party COM libraries are just not particularly common anymore.