ShuriZma
/
dolphin
mirror of https://github.com/dolphin-emu/dolphin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix a style guide oversight 

Fixes an oversight which says to not use mult-line comments.
This commit is contained in:
Lioncash 2014-07-27 06:19:25 -04:00
parent 96cfbd1bb0
commit adf3543a57
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Contributing.md
View File

@ -34,6 +34,7 @@ Following this guide and formatting your code as detailed will likely get your p
- The opening brace for namespaces, classes, functions, enums, structs, unions, conditionals, and loops go on the next line. - The opening brace for namespaces, classes, functions, enums, structs, unions, conditionals, and loops go on the next line.
- With array initializer lists and lambda expressions it is OK to keep the brace on the same line. - With array initializer lists and lambda expressions it is OK to keep the brace on the same line.
- References and pointers have the ampersand or asterisk against the type name, not the variable name. Example: `int* var`, not `int *var`. - References and pointers have the ampersand or asterisk against the type name, not the variable name. Example: `int* var`, not `int *var`.
- Don't use multi-line comments (`/* Comment text */`), use single-line comments (`// Comment text`) instead.
- Don't collapse single line conditional or loop bodies onto the same line as its header. Put it on the next line. - Don't collapse single line conditional or loop bodies onto the same line as its header. Put it on the next line.
- Yes: - Yes: