4 ms·
We compile our product with GCC, Clang and MSVC, and we need some #ifdefs. MSVC for years was far behind GCC/Clang, recently Microsoft did a really good job and
by wmu 10y ago
We compile our product with GCC, Clang and MSVC, and we need some #ifdefs. MSVC for years was far behind GCC/Clang, recently Microsoft did a really good job and they catching up. But some #ifdefs are still needed. :)
I agree that C++11 was a leap (older C++ was terrible). However, both C++14 and C++17 are just a sets of smaller or bigger improvements.
- Koshkin 10y agoI have never understood this stance 'C++ was terrible'. Even with the introduction of destructors - and exceptions! - C++ became way ahead of other languages of its time and almost instantly secured its well deserved place in the minds of programmers.
- wmu 10y agoOK, maybe "terrible" is too strong adjective. What about "cumbersome"? :) C++11 allowed to get rid off many silly workarounds and introduced, among many others, threads and rvalues.
- pjmlp 10y agoIt was, but mostly regardig portability. One of the reasons I found some pleasure writing Java instead of C++, even before it got a JIT, was the portability story. Writing portable C++ code across the many commercial compilers available back in the days when the only standard was the C++ARM book, wasn't particularly fun.