Documentation/4.1/Developers/Style Guide/Cpp - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:23:22Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

JChris.FillionR at 04:32, 22 June 2012

2012-06-22T04:32:04Z

JChris.FillionR at 04:31, 22 June 2012

2012-06-22T04:31:45Z

JChris.FillionR at 21:16, 1 June 2012

2012-06-01T21:16:14Z

JChris.FillionR at 21:15, 1 June 2012

2012-06-01T21:15:21Z

JChris.FillionR: 4.0 -> 4.1

2012-04-12T04:42:55Z

4.0 -> 4.1

New page

{{documentation/underconstruction}}

= Indentation =
Configure your text editor to do VTK style indentation:
* [http://www.vtk.org/Wiki/Elisp_Code_for_VTK-Style_C_Indentation Emacs]
* [http://wiki.na-mic.org/Wiki/index.php/User:Pieper Vi/Vim]
* [http://www.vtk.org/Wiki/VTK_FAQ#How_do_I_get_my_C.2B.2B_code_editor_to_do_VTK-style_indentation.3F Visual Studio]

= Naming =
* Local variable should start with a lower case.
** For example:

void vtkSlicerSliceLogic::SetForegroundLayer(vtkSlicerSliceLayerLogic *ForegroundLayer) // wrong!

should be

void vtkSlicerSliceLogic::SetForegroundLayer(vtkSlicerSliceLayerLogic *foregroundLayer)

* Member variable should start with a capital letter, and in implementation should be used in conjunction with 'this->' convention
** For example

class Node {
Object &Foo();
Object Bla;
};
Object& Node::Foo()
{
return this->Bla;
}

= References =
* https://secure.wikimedia.org/wikipedia/en/wiki/Indent_style#GNU_style
* https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml

= Tools =

* http://universalindent.sourceforge.net/
* http://uncrustify.sourceforge.net/

{{ambox|text=
Use common sense and BE CONSISTENT.

If you are editing code, take a few minutes to look at the code around you and determine its style.
If they use spaces around their if clauses, you should, too.
If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too.

The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you are saying, rather than on how you are saying it. We present global style rules here so people know the vocabulary. But local style is also important. If code you add to a file looks drastically different from the existing code around it, the discontinuity throws readers out of their rhythm when they go to read it. Try to avoid this.

OK, enough writing about writing code; the code itself is much more interesting. Have fun!

<i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C++ Style Guide]</i>
}}

← Older revision		Revision as of 07:23, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	Use common sense and BE CONSISTENT.		Use common sense and BE CONSISTENT.

← Older revision		Revision as of 04:32, 22 June 2012
Line 10:		Line 10:

	<i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C++ Style Guide]</i>		<i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C++ Style Guide]</i>
		+

	__TOC__		__TOC__

@@ Line 1: / Line 1: @@
 Use common sense and BE CONSISTENT.
@@ Line 13: / Line 10: @@
 <i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C++ Style Guide]</i>
-}}
 = Indentation =

@@ Line 1: / Line 1: @@
-{{documentation/underconstruction}}
+__TOC__
 {{ambox|text=
@@ Line 52: / Line 52: @@
 * http://universalindent.sourceforge.net/
 * http://uncrustify.sourceforge.net/