Decide on coding style and conventions

[trigger-segfault]

OpenLRR is in need of style guidelines, and an accompanied .editorconfig to enforce them.

Along with this, naming conventions should be decided upon. This includes how to handle the 20-year-old naming conventions of the GODS 98 engine, and conventions in LegoRR that are visible through similar practices seen in GODS (i.e. name tables reflect the names of real enum/flag values).

(this issue is a work in progress, and is still being written)

---

All of this is open for discussion. Please give feedback even if you believe your suggestions to be minor nitpicks.

Entries with an unchecked box, are still mostly undecided. Entries with a checked box and (final), are the only standards not open for discussion

Coding style

General formatting

• Max line width: ?
• Tabs or spaces: tabs
• Indent size: 4 (final)
• New line type: crlf (final)
• Text encoding (of files): utf-8 (final)
• BOM (byte order mark): no (final)

C/C++ formatting

Braces

• Opening, Definitions: new line
  • Namespaces, functions, types
• Opening, Assignment blocks: same line
  • Arrays, inline structs, initializer lists
• Opening, Code blocks: same line
• Closing keyword, do while: same line
  • Avoids ambiguity with while blocks.
  • Prefer empty line before closing block.
• Closing keyword, else/catch/etc.: new line

Spacing

• Between, block keyword/parentheses: yes
• Between, function (keyword)/parentheses: no
• Before, Open brace: yes
• After, Closing brace: yes
• Before, comma or semicolon: no
• After, comma or semicolon: yes
• Between, C-style casts: no

Fluff

• Comma after final, enum value: yes
• Comma after final, array definition value: yes
• Comma after final, struct initializer value: ?