Parsing C++ is literally undecidable (2013)

Re:Parsing C++ is literally undecidable (2013) by atilaneves on Friday October 04, 2019 @09:56AM (#21157717)

I went back to C++14 a few years ago after writing D and it was painful. The only addition to C++17 that made my life easier was `void_t`, but even then it's not even close.

Having to deal with headers again and C++'s templates was torture.

Did C++ close the gap? Yes. However, I can still write D 2-3x faster than I can write C++. It's similar to how I'm 2-3x more productive in C++ than in C.

[ Parent | on HN ]

Re:Parsing C++ is literally undecidable (2013) by pjmlp on Friday October 04, 2019 @05:49PM (#21162199)

I only use C++ alongside Java and .NET, when they need an extra help.

The problem with D in its current state is that its tooling isn't match for OS SDKs + IDE + libraries, beyond the typical POSIX daemon scenarios, unless one is willing to put some effort into it.

So it is hard to catch up to C++, specially after all major compilers reach C++20 compliance.

[ Parent | on HN ]