StuBS
|
Similar to Google C++ Style Guide but with following exceptions:
#pragma once
instead of #include
guardsThe code should be self-documenting, don't state the obvious! However, this does not make comments superfluous: Since good naming is sometimes not enough, more advanced parts need to be documented, so any operating system developer should be able to easily understand your code.
char* variable_name;
const int CONST_VALUE = 42;
class
/struct
/namespace
/enum
): Capital letter, camel case class SomeClassName;
void someFunctionName();
void interrupt_handler(int vector);
folder/classname.cc