Difference between revisions of "Slicer3:Style"

From NAMIC Wiki
Jump to: navigation, search
 
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/")
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
A few things to keep in mind:
+
<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Style  here]</font></big>
 
 
* All C++ classes must conform to the style conventions of their parent classes.
 
** In most cases for Slicer Base, this means following VTK coding conventions including naming, indentation, and other issues discussed at the [http://www.vtk.org/Wiki/VTK_Coding_Standards VTK Coding Standards] page.
 
** For command line modules implemented in ITK, follow the conventions defined in Insight/Documentation/Style.pdf from the ITK distribution.
 
 
 
Highlights of the policies:
 
* avoid acronyms in class and method names
 
* use 2 spaces for indentation, not tabs
 
* think carefully about the reusability of your class hierarcies
 
* comment your code extensively
 

Latest revision as of 18:07, 10 July 2017

Home < Slicer3:Style

Note: We are migrating this content to the slicer.org domain - The newer page is here