Originally posted by coder
View Post
Anyway, I like most of the additions in C++11, but I feel like they really needed to draw a hard line that any additions or enhancements must make the language: easier to use safely, enhanced portability, or address some major, practical limitation or hurdle involved in using C++03. If they'd done that, I think it would've had more benefit for the long-term health of the language than larding it up with crap like if-init and structured bindings (to pick on the new standard).
Seriously, you can write C++11 that's almost incomprehensible to a knowledgeable C++03 programmer and boost user. That's a problem, IMO.
Seriously, you can write C++11 that's almost incomprehensible to a knowledgeable C++03 programmer and boost user. That's a problem, IMO.
However, you at least appear to feel it's the C++ Standards Committee's duty to embrace your personal coding standard -- whatever that is -- and inflict it upon the rest of Known Space. But there are software tools that have the same effect, are readily customizable from the safety and convenience of your own home, and can be integrated into IDE's such as Eclipse and run automagically if such is your desire.
Seriously. I worked an ISO 90001 medical project once where that is exactly what we did: The IDE's editor and it's formatting standard were required, and every line of code was required to pass our customized Parasoft Eclipse static analyzer. It wasn't rocket science. And although I prefer the "Latest and Greatest" C++ standard (and emacs...) for my personal projects, I'll likely be starting some more esoteric external work shortly and will fersure incorporate some sort of static analysis tool if I do. See https://en.wikipedia.org/wiki/List_o..._code_analysis -- there's something there for everyone.
Comment