Add styleguide

First revision, needs lots of discussion!

Author: LB--

src/README.md

@@ -0,0 +1,22 @@
+Style Guide & Coding Conventions
+================================
+- Indentation is to be consistently four spaces, not tabs or a mixture of spaces and tabs.
+- All files are to have a single blank line at their end, if possible.
+- Prefer C++11 features to C++03 features when possible, and avoid deprecated language features.
+- Prefer use of `class` to `struct` for declaring classes (this means you need to explicitly specify public inheritance).
+- Prefer to use file extensions .cpp and .hpp to aid in GitHub's language recognition algorithms (using .h may cause the file to be detected as C rather than C++)
+- Prefer `lowercase` namespace, parameter, and local variable names.
+- Prefer `UpperCamelCase` class and member function names
+- Prefer `lower_case_underscore` private member names
+- Avoid using raw pointers when possible
+- Prefer creating `using` declarations to using raw primitive types
+- Avoid use of exceptions when possible
+- Avoid ambiguous or non-obvious public interfaces that would otherwise require documentation
+- Prefer code that makes less assumptions and allows more flexibility to client code
+- Prefer using e.g. functions defined in `<algorithm>` to using common idioms - this allows refactoring to be more obvious and/or straightforward
+- First design abstract/high-level/object-oriented code, and optimize later as needed
+- Use nameless scopes in functions to emphasize the lifetime of RAII objects
+- Place source file helper functions/classes in anonymous namespaces AND declare them static, so as to avoid name/symbol conflicts across irrelevant source files
+- Keep clear the separation between client and server behaviors and responsibilities
+
+To suggest changes to this guide, fork the project, make amendments, submit the pull request, and partake in discussion of the changes.