News for hackers. Stuff that matters.
Re:Is the C++ preprocessor still needed? by EGreg on Tuesday May 09, 2017 @08:17PM (#14304970)
Lambdas. Concepts. Ten types of casts. Templates of templates. Everything and the kitchen sink is in there.

You need a language lawyer to figure out anything but the most basic interactions. For example,

1. What's the practical difference between an abstract class and an interface?

2. When do you have a copy constructor run instead of a cast on initialization if both are defined?

3. When would you use a non-virtual destructor?

What happens when you hire people? Isn't it better to have a small language that everyone understands in its entirety, and has to go out of their way to surprise you?

Re:Is the C++ preprocessor still needed? by wfunction on Tuesday May 09, 2017 @08:27PM (#14305029)
> 1. What's the practical difference between an abstract class and an interface?

Interface? You are talking about the C++ language, right?

Re:Is the C++ preprocessor still needed? by kobeya on Tuesday May 09, 2017 @11:14PM (#14305657)
The funny thing is I just good faith assumed that this was some new feature being added in C++17 that I'd now have to figure out how to use.
Re:Is the C++ preprocessor still needed? by santaclaus on Tuesday May 09, 2017 @11:28PM (#14305712)
> Interface? You are talking about the C++ language, right?

If Sutter's metaclasses get into C++20 C++ could indeed have an equivalent to interface enforced by the compiler.

Re:Is the C++ preprocessor still needed? by Ace17 on Wednesday May 10, 2017 @01:18AM (#14306073)
> What's the practical difference between an abstract class and an interface?

C++ doesn't have "interfaces". No wonder you think there's too much stuff.

Re:Is the C++ preprocessor still needed? by jsolson on Wednesday May 10, 2017 @03:09AM (#14306400)
Ironically, Java, which does have both, has a clear and unambiguous distinction between the two.