5 ms·
Note that while support for anything post C89 used to be spotty at best, the Visual Studio situation has improved in recent years, see e.g. [1]. [1] https://de
by cygx 4y ago
Note that while support for anything post C89 used to be spotty at best, the Visual Studio situation has improved in recent years, see e.g. [1].
[1] https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/ https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-...
- cryptonector 4y agoYes, I'm aware. But a friend has to support very old VC and Windows. Don't ask. Point is that Microsoft's failure to support C99 a decade ago is still annoying.
- pjmlp 4y agoIt wasn't a failure, the point of Visual C++ is to be good at supporting C++ and cleary communicated as a business decision. https://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/ https://herbsutter.com/2012/05/03/reader-qa-what-about-vc-an...
- cryptonector 4y agoBut it was also required for, e.g., building supported kernel modules. It ended up imposing on others. It was cheap for MSFT, I get that, and this is life, but I also get to point out that this happened.
- pjmlp 4y agoSince Vista that a C++ subset is allowed for kernel code (/kernel) and nowadays there are template libraries like WIL.