Skip to content

Code rules

Mikulas Florek edited this page Jul 31, 2015 · 10 revisions
  • Quality is the most important feature.
  • Write for readers - code is read and debugged many more times than it is edited.
  • Consistency - look at the way things are already done - formatting, filenames, structure, ...
  • Keep it simple, stupid.
  • Templates, C++11, ... use whatever you think is reasonable if it works on all supported platforms.
  • Asserts should not be triggered by data and data can not cause crashes.
  • Use clang-format, there is a config for it
Clone this wiki locally