openmw.org

https://isocpp.org/blog/2015/09/bjarne- ... guidelines

This morning in his opening keynote at CppCon, Bjarne Stroustrup announced the C++ Core Guidelines , the start of a new open source project on GitHub to build modern authoritative guidelines for writing C++ code. The guidelines are designed to be modern, machine-enforceable wherever possible, and open to contributions and forking so that organizations can easily incorporate them into their own corporate coding guidelines.

Yay, another standard... and you can fork it! </snark>

Thanks, as a non-c++ guy stuff like this is helpful when trying to hack on code. I can rtfm, know the theory, but end up with bad habits from just doing something so it just works. I know what I can do, just not what I should!

Personally I really hate this kind of stuff but after working on a commercial project… majority of C++ programmers is just bad. This kind of tool may help, but it will never prevent terrible code from showing up.

We're really strict about things at work, no cowboys. You get used to it after awhile, then you realize that it is safest, sanest with the best performing software you've written with the benefit of being readable and maintainable.

To this end, it isn't a language's fault that shit code is written but the discipline of its user.

There is, however, one exception: Java... may it die a fiery death.

sirherrbatka wrote:Personally I really hate this kind of stuff but after working on a commercial project… majority of C++ programmers is just bad. This kind of tool may help, but it will never prevent terrible code from showing up.

You can say that sentence removing the "C++" part. Unfortunately, in C++ it is more evident.

psi29a wrote:There is, however, one exception: Java... may it die a fiery death.

This is also my experience!

One day we may be able to run openmw through this new tool, whenever it's released.
Of course, without switching to c++11 or 14 we'll have hundreds of thousands of lines of output.

psi29a wrote:Yay, another standard... and you can fork it! </snark>

or use the google c++ style guide: https://google.github.io/styleguide/cppguide.html

otoh google is more and more switching away from c++ to go for obvious reasons.