Re:C++ and the Culture of Complexity (2013)
by zach43 on Wednesday January 31, 2018 @11:17AM
(#16274954)
One fairly common example of a bad C++ design edge case is the “Most Vexing Parse” problem [0].
I frequently find myself constructing objects using the () syntax will produce parse errors as the compiler is expecting a function declaration. Then replacing the () with {} just fixes it. It’s really frustrating that bad design like this is just maintained as a stumbling block for new users, instead of being fixed.
I frequently find myself constructing objects using the () syntax will produce parse errors as the compiler is expecting a function declaration. Then replacing the () with {} just fixes it. It’s really frustrating that bad design like this is just maintained as a stumbling block for new users, instead of being fixed.
[0] https://en.wikipedia.org/wiki/Most_vexing_parse