-
Notifications
You must be signed in to change notification settings - Fork 773
Some thoughts about C++ #788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This seems to be a purely personal opinion with no concrete suggestions for changing anything. The idea of separating "classic" features from the more modern ones would be highly controversial, arguably the modern features make code clearer and simpler. https://github.com/cplusplus/draft/wiki/How-to-tell-if-an-issue-is-editorial |
I mean new grammar and classic grammar can be all there, but some of the new grammar is not so strict, I call them candy grammar, what about to seperate candy grammar and classic grammar in language level, something like namespace. |
That's definitely not an editorial change, so this is the wrong place to propose it. It's also a terrible idea. Just because you don't value the new language features doesn't mean they should be relegated. |
|
This is the wrong place to discuss your opinions on good use of C++. Just because you don't like modern C++ style does not make it inferior, and this is the wrong place to discuss it. Please find somewhere else, e.g. https://groups.google.com/a/isocpp.org/forum/#!forum/std-discussion |
Uh oh!
There was an error while loading. Please reload this page.
C is perfect.
C++ tries to take the advantage of semantic, so genius grammar is in demand :)
C++11 introduced some grammar candies:
initilizer_list
,auto
,for (auto e:v)
, etc. Candy is candy, you can't take candy grammar seriously. The classic grammar should be taken seriously, so it should not be mixed with the candy grammar. If you mix classic grammar with candy grammar, it becomes less classic, i.e. not classic.I think seperating them explicitly will make C++ more excellent.
STL is good enough :)
The text was updated successfully, but these errors were encountered: