News for hackers. Stuff that matters.
Re:Why C++ sucks (2016 edition) by bjz_ on Monday February 22, 2016 @02:41AM (#11149204)
> Of all the complaints I can think of regarding C++, the one I care least about is the difficulty in disambiguating the grammar

Compile time speed? Refactoring? Jump-to-definition? Autocomplete? Intellisense? Those are all important for UX, and a tricky-to-parse grammar makes those things mighty challenging.

Re:Why C++ sucks (2016 edition) by roel_v on Monday February 22, 2016 @04:12AM (#11149533)
Visual Studio does an almost-perfect job of this, and what is missing is not because of the parsability of C++. What's your point?
Re:Why C++ sucks (2016 edition) by zzalpha on Monday February 22, 2016 @09:07AM (#11150832)
Those are all examples of semantic analysis (which is also a problem with C++, but has little to do with the grammar). A tricky grammar is simply a parsing problem.
Re:Why C++ sucks (2016 edition) by nan0a on Wednesday February 24, 2016 @12:46PM (#11168607)
C++ compilation times are absolutely ridiculous, esp. when compared to something like D which has greater expressiveness in its compile-time features.
Re:Why C++ sucks (2016 edition) by msbarnett on Monday February 22, 2016 @09:05PM (#11155929)
Semantic analysis is a post-parse task. Difficulty of constructing the parse tree has no impact on consumers of the parse tree.