3 ms·
> I'm a native Win32 developer, have been one for a few decades, and know quite a few others still using MSVC6 Doesn't that tie you to a really old C runtime,
by josephcsible 4y ago
> I'm a native Win32 developer, have been one for a few decades, and know quite a few others still using MSVC6
Doesn't that tie you to a really old C runtime, and aren't security holes often found in the C runtime?
- adzm 4y agoIt links dynamically to msvcrt.dll which is updated as part of the os. I believe it still gets updates as long as it doesn't break the ABI. Modern vc++ links with the universal CRT which is an independently updated msvcrt distribution.
- dwattttt 4y agomsvcrt.lib includes things other than direct imports to msvcrt.dll; bugs in that code are going to be linked into your binary at compile time.
- ygra 4y agoNote: https://devblogs.microsoft.com/oldnewthing/20140411-00/?p=1273 https://devblogs.microsoft.com/oldnewthing/20140411-00/?p=12...
- userbinator 4y agoOf course he has to toe the company line. But the truth is far simpler.
- samus 4y agoSimilar problem to Java applications directly accessing internal JDK packages, and then breaking once access was restricted.
- ranger_danger 4y agoBoth static and dynamic linking to a newer runtime (as they are versioned) will break backwards compatibility. For newer OS features you need, you can always GetProcAddress() the needed functions at runtime instead. The real downside to staying on VC6 is all the compilers' ancient optimizations, or lack thereof.
- deleted 4y ago[deleted]
- jcelerier 4y agoA quick Google check seems to yield only one CVE in msvcrt.dll in 2012, wouldn't call this "often" especially for a DLL which is likely among the top 5 most used in the world