mirror of
https://github.com/yuzu-emu/yuzu.git
synced 2024-07-04 23:31:19 +01:00
Resolve doxycomment duplication debate
I believe putting comments in the headers has won by a good margin, with everyone other than me preferring it, so time to enshrine it.
This commit is contained in:
parent
846dc72a37
commit
43f7f37d93
1 changed files with 1 additions and 0 deletions
|
@ -27,6 +27,7 @@ Follow the indentation/whitespace style shown below. Do not use tabs, use 4-spac
|
||||||
### Comments
|
### Comments
|
||||||
* For regular comments, use C++ style (`//`) comments, even for multi-line ones.
|
* For regular comments, use C++ style (`//`) comments, even for multi-line ones.
|
||||||
* For doc-comments (Doxygen comments), use `/// ` if it's a single line, else use the `/**` `*/` style featured in the example. Start the text on the second line, not the first containing `/**`.
|
* For doc-comments (Doxygen comments), use `/// ` if it's a single line, else use the `/**` `*/` style featured in the example. Start the text on the second line, not the first containing `/**`.
|
||||||
|
* For items that are both defined and declared in two separate files, put the doc-comment only next to the associated declaration. (In a header file, usually.) Otherwise, put it next to the implementation. Never duplicate doc-comments in both places.
|
||||||
|
|
||||||
```cpp
|
```cpp
|
||||||
namespace Example {
|
namespace Example {
|
||||||
|
|
Loading…
Reference in a new issue