From ed0a0a68f2361047c33ce37dece7b20eda1d62a0 Mon Sep 17 00:00:00 2001
From: Damien GERARD <damien@iwi.me>
Date: Wed, 15 Jul 2015 11:55:49 +0200
Subject: [PATCH] COMTRIBUTING: Prefer C++11/14 coding style

---
 CONTRIBUTING.md | 37 ++++++++++++++++++++++++++++++++++++-
 1 file changed, 36 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 35f1c259..6e914a4c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -129,6 +129,30 @@ GOOD:
 
 * Prefer enums for integer constants
 
+* Use initialization with curly braces
+
+GOOD:
+```c
+MyClass instance{10.4};
+```
+BAD:
+```c
+MyClass instance(10.4);
+```
+
+* Always use `empty()` for testing if a string is empty or not
+
+GOOD:
+```c
+if (not string.empty())
+	...
+```
+BAD:
+```c
+if (string != "")
+	...
+```
+
 
 
 ####NAMING CONVENTIONS
@@ -164,7 +188,7 @@ GOOD:
       int _pPrivateAttribute;
       float _pAccount;
 ```
-	  
+
 * Always prefer a variable name that describes what the variable is used for
 
 GOOD:
@@ -195,6 +219,16 @@ BAD:
 
 ####BEST PRACTICES
 
+* Use C++11/14 whenever it is possible
+
+* Use C++11 member initialization feature whenever it is possible
+```c
+class Foo
+{
+	int value = 0;
+};
+```
+
 * Prefer this form :
 ```c
       ++i
@@ -211,6 +245,7 @@ BAD:
   be checked. Wherever possible, use a SmartPtr instead of old-school pointers.
 
 * Avoid using new if you can use automatic variable.
+  However, avoid `shared_ptr` as much as possible. Prefer `unique_ptr` instead.
 
 * Don't place any "using namespace" directives in headers