Changeset 49 in pacpusframework

Timestamp:

Jan 9, 2013, 8:57:11 AM (12 years ago)

Author:

Marek Kurdej

Message:

Coding style: curly brackets.

File:

• trunk/CODING_STYLE.txt (modified) (3 diffs)

trunk/CODING_STYLE.txt

@@ -18 +18 @@
     #endif // PACPUS_EXAMPLE_H
 * use C++-style comments (//)
+* ALWAYS use curly brackets with statements if, for, etc.
+* use curly brackets {} as follows:
+    * on the same line with:
+        - namespace {
+        - statements if, for, etc.
+            if (cond) {
+            } else if (cond2) {
+            } else {
+            }
+    * on the next line with:
+        - classes
+        - function and method definitions
+        - local scope blocks
+            class A
+            {
+                void fun A;
+                
+                struct AB
+                {
+                };
+                
+                void fun A
+                {
+                }
+            };
 * write Doxygen-style comments as much as possible, put it in the header file if possible, add developer-only comments in source file
 * use Java-style Doxygen comments, i.e. @returns over \returns
@@ -63 +88 @@
     int mMemberA;
 };
+
 } // namespace pacpus
 
@@ -87 +113 @@
 {
     int someIntegerVariable;
+    
+    if (a) {
+        a();
+    } else {
+        b();
+    }
+    
+    if (isConditionSatisfied()) {
+        doSomething();
+        return 0;
+    }
+    return 1;
 }