C++ Dev Ecosystem 2021

Re:C++ Dev Ecosystem 2021 by xvilka on Monday July 19, 2021 @09:57PM (#27889353)

It's surprising how so many people still use MSVC when there's clang-cl[1]. Both Google and Mozilla use it for producing binary releases for Windows for years already[2][3]. MSVC has poor track record on following standards and lacked ASAN etc support until recently. And Visual Studio now can integrate with it smoothly [4].

[1] https://clang.llvm.org/docs/MSVCCompatibility.html

[2] https://blog.llvm.org/2018/03/clang-is-now-used-to-build-chr...

[3] https://blog.mozilla.org/nfroyd/2019/04/25/an-unexpected-ben...

[4] https://docs.microsoft.com/en-us/cpp/build/clang-support-msb...

[ Parent | on HN ]

Re:C++ Dev Ecosystem 2021 by TinkersW on Monday July 19, 2021 @11:53PM (#27889895)

MSVC track record is poor, but that isn't relevant to today, it is actually ahead of GCC/Clang for tracking the standard if anything.

You can use both MSVC/Clang-CL..

The primary reason I find to still use MSVC is that it compiles faster.

[ Parent | on HN ]

Re:C++ Dev Ecosystem 2021 by pjmlp on Tuesday July 20, 2021 @01:22AM (#27890350)

If you want do the Windows development with raw Win32 C APIs and zero tooling that is.

Most of us live on .NET and C++ mixed code bases, and enjoy our IDE tooling for all levels of Windows stack.

[ Parent | on HN ]

Re:C++ Dev Ecosystem 2021 by userbinator on Monday July 19, 2021 @10:51PM (#27889603)

Speaking from experience, because MSVC (and also ICC) is far more sane with how it interpets undefined behaviour.

[ Parent | on HN ]

Re:C++ Dev Ecosystem 2021 by xvilka on Tuesday July 20, 2021 @01:17AM (#27890325)

Relying on UB in programs is a recipe for disaster. It should be avoided rather than workarounded by compiler. There's UBSAN, various static analysis tools to fish out UB, developers should use them instead.

[ Parent | on HN ]