C++ Codying Style Rules - Revizia istoricului

Rhobincu: /* Language Specific Requirements */

2018-03-04T18:32:20Z

Language Specific Requirements

Rhobincu: /* Code Formatting and Revision Control */

2018-03-04T18:31:19Z

Code Formatting and Revision Control

Rhobincu: /* Namespaces */

2018-03-04T18:29:58Z

Namespaces

Rhobincu: /* Class Names */

2018-03-04T18:29:24Z

Class Names

Rhobincu: /* General Rules */

2018-03-04T18:27:53Z

General Rules

Rhobincu: Pagină nouă: = General Rules = # Use 4 spaces for aligning code instead of tabs. '''Caution''': configuring the editor to size the tab character as four spaces is not enough. You must force th...

2018-03-04T18:27:17Z

Pagină nouă: = General Rules = # Use 4 spaces for aligning code instead of tabs. '''Caution''': configuring the editor to size the tab character as four spaces is not enough. You must force th...

Pagină nouă

= General Rules =

# Use 4 spaces for aligning code instead of tabs. '''Caution''': configuring the editor to size the tab character as four spaces is not enough. You must force the editor to insert four spaces when you press TAB.
# Maximum line length must be set to 120 characters.
# Avoid using inner classes unless they are very short and are only used in the particular class they're defined in.
# Use of lambda expressions is encouraged but not mandatory.
# Use of for-each structures, where applicable, is mandatory over user iterators or old style i=0->n-1.
# All source files must begin with the following licence header:
/* ************************************************************************
* Copyright (C) Philro Vision SRL - All Rights Reserved 2016 - <creation_year>
* Unauthorized copying of this file, via any medium is strictly prohibited
* Proprietary and confidential.
**************************************************************************/

= Documentation =
All classes and members must have Doxygen comments describing their usage and parameters and return value in the header file.

= Naming scheme =

Names should clearly express meaning and usage of the variable, method or class. Avoid using shortcuts! You have autocomplete functions in your IDE, use it! So don't use <code><strike>cmd</strike></code> instead of <code>command</code> or <code><strike>retVal</strike></code> instead of <code>returnValue</code>. The only exceptions are well established names for index iterators: i, j, k and coordinates names: x, y, z.

== Variable Names ==
# Local method variables must start with a lowercase character and follow the camel-case naming scheme: <code>megaImportantVariable</code>
# Instance variables (non-static fields) must begin with a lowercase '''m''' (for "member") and follow the camel-case naming scheme: <code>mMegaImportantField</code>
# Class variables (static, non-const fields) must begin with a lowercase '''s''' and follow the camel-case naming scheme: <code>sMegaImportantStaticVariable</code>
# Class constants (static const fields) must be all uppercase and follow the snake-case naming scheme: <code>MEGA_IMPORTANT_CONSTANT</code>
# In order to improve readability of the code, acronyms should not appear all caps in variable names: <code>newUrlForFile</code> instead of <code><strike>newURLForFile</strike></code>

== Method Names ==
All method names (except for constructors) must start with a lowercase character and follow the camel-case naming scheme: <code>doTheWork()</code>

== Class Names ==
All class names must start with an uppercase character and follow the camel-case convention: <code>MyMegaClass</code>

== Namespaces ==
Namespaces must be all lowercase and follow the snake-case convention: <code>philro::ocr_engine</code>

= Bracketing =
The bracketing style used is [https://en.wikipedia.org/wiki/Indent_style#Variant:_1TBS_.28OTBS.29 OTBS] (One True Brace Style) with the observation that the open bracket is always at the end of the begin statement, even for method and classes:
<syntaxhighlight lang="c++">
class Foo {
}
</syntaxhighlight>

instead of

<syntaxhighlight lang="c++">
class Foo
{
}
</syntaxhighlight>

There must '''ALWAYS''' be brackets placed after control blocks (like <code>for</code> and <code>if</code>), even if the controlled block has only one statement, with the exception of the case where the entire block is short enough to be written in one line. The following is acceptable:
<syntaxhighlight lang="c++">
for (vector<vector<uint8_t>> &myList : listOfLists) myList.clear();
</syntaxhighlight>

This is not:

<strike>
<syntaxhighlight lang="Java">
for (vector<vector<uint8_t>> &myList : listOfLists)
myList.clear();
</syntaxhighlight>
</strike>

= Spacing =

A space character must be inserted in the following situations:
* before an open bracket;
* after an open bracket (if there is something else on that line);
* after the keywords <code>for</code>, <code>if</code>, <code>else</code>, <code>while</code> (in while blocks) and <code>do</code> (in do-while blocks);
* before and after binary operators with the exception of the dot (.) operator.

= Language Specific Requirements =

# Use <code>#pragma once</code> instead of old style macro include guards.
# We prefer the use of references over pointers, when possible.
# Use fixed width data types (<code>int8_t</code>, <code>uint16_t</code>) instead of default primitive types (<code>int</code> or <code>unsigned short</code>).
# The use of <code>auto</code> type is permitted where the type is easy to determine by the reader.

= Code Formatting and Revision Control =

ALWAYS run an automatic formatting operation on the written code before a Git commit.

The following file may be imported in Netbeans for the necessary configuration: [[File:Netbeans_C++.zip]]

The following file may be imported in CLion Idea for the necessary configuration: [[File:clion.xml]]

← Versiunea anterioară		Versiunea de la data 4 martie 2018 18:31
Linia 76:		Linia 76:
	= Code Formatting and Revision Control =		= Code Formatting and Revision Control =

−	ALWAYS run an automatic formatting operation on the written code before a Git commit.	+	Configure your IDE and '''ALWAYS''' run an automatic formatting operation on the written code before a Git commit.
−
−	~~The following file may be imported in Netbeans for the necessary configuration: [[File:Netbeans_C++.zip]]~~
−
−	~~The following file may be imported in CLion Idea for the necessary configuration: [[File:clion.xml]]~~

@@ Linia 73: / Linia 73: @@
 # Use fixed width data types (<code>int8_t</code>, <code>uint16_t</code>) instead of default primitive types (<code>int</code> or <code>unsigned short</code>).
 # The use of <code>auto</code> type is permitted where the type is easy to determine by the reader.
 = Code Formatting and Revision Control =
 Configure your IDE and '''ALWAYS''' run an automatic formatting operation on the written code before a Git commit.

@@ Linia 28: / Linia 28: @@
 == Namespaces ==
-Namespaces must be all lowercase and follow the snake-case convention: <code>philro::ocr_engine</code>
+Namespaces must be all lowercase and follow the snake-case convention: <code>aces::ocr_engine</code>
 = Bracketing =

@@ Linia 24: / Linia 24: @@
 All method names (except for constructors) must start with a lowercase character and follow the camel-case naming scheme: <code>doTheWork()</code>
-== Class Names ==
+== Structures Names ==
-All class names must start with an uppercase character and follow the camel-case convention: <code>MyMegaClass</code>
+All class, structures, unions and enumumerations names must start with an uppercase character and follow the camel-case convention: <code>MyMegaClass</code>
 == Namespaces ==

@@ Linia 6: / Linia 6: @@
 # Use of lambda expressions is encouraged but not mandatory.
 # Use of for-each structures, where applicable, is mandatory over user iterators or old style i=0->n-1.
 = Documentation =