vitaut

These are trivial issues compared to major safety and usability flaws inherited from C that I mentioned. BTW the C grammar is not context-free either. The compilation speed is mostly due to header system which is again a C heritage, not because the C++ grammar is undecidable. And template error messages are much better now in modern compilers such as Clang. As for the const, its semantics is the same as in C.

Could you give an example?

From my experience, if you need to write many exception handlers then you have a problem in your design as you are using exceptions where you should have used explicit control flow. There is nothing fundamentally wrong with the exceptions and they are used in most modern languages, not only C++.

Actually avoiding C++ pitfalls is not that difficult as most of them come from C: manual memory management, macros, varargs, unsafe casts. In fact C++ provides safe alternatives to many of the unsafe C constructs, so if you stick to them you are fine.

Since the readme doesn't give much details, I recommend looking at the example: https://github.com/minrk/clingkernel/blob/master/cling.ipynb

I think you are nitpicking here. There is a figure of speech called "hyperbole" which "the use of exaggeration as a rhetorical device" (http://en.wikipedia.org/wiki/Hyperbole).

BTW I don't understand why you refuse to comment on the original post. The author could clarify to you what exactly he meant.

Calling C, C++ and Java "the most different programming languages in the world" is, of course, an exaggeration, but it's hard to disagree that the way you write idiomatic code in the three language is completely different.

In many cases you don't need preprocessor for this even in C++. For example you can detect the availability of system functions using function overloading as described in http://zverovich.net/2015/03/13/reliable-detection-of-strerr...

There is a package manager for C++ called Biicode: https://www.biicode.com/

Looks like everything went according to the plan =).

And here's the official announcement: https://bits.debian.org/2015/04/jessie-released.html

I'd say more: "X that noone uses, now written in language Y that noone uses".

When you develop something you consider not only the features of the language itself, but also the availability of libraries in this particular language. There is a large amount of high-quality C++ libraries and C++ can consume C libraries seamlessly. In most other languages you need to write often unsafe bindings to connect to C.

D simply doesn't have enough libraries to make it a viable choice except maybe for some niche area. For example, there are only 6k D repos on GitHub (https://github.com/search?utf8=%E2%9C%93&q=language%3AD&type...) compared with 340k C++ repos. Also any high-performance code (at least in the area I'm working) is written in C++ or, sometimes, in C.