Difference between revisions of "Cpp Coding Standards"

From Apache OpenOffice Wiki
Jump to: navigation, search
(sorting topics)
m (Identifying Rules)
Line 3: Line 3:
  
 
=== Identifying Rules ===
 
=== Identifying Rules ===
To make it easier to talk about the rules, each one gets an identifier. Because, items can be added or sorted out, such ids should not be just cardinal numbers.
+
To make it easier to talk about the rules, each one gets an identifier. Because items can be added or sorted out, such ids should not be just cardinal numbers.
  
 
Here each rule belongs to a topic, which has an id, and has an id itself.
 
Here each rule belongs to a topic, which has an id, and has an id itself.
Line 9: Line 9:
  
 
----
 
----
 +
 
=== Topics by Problem Domain ===
 
=== Topics by Problem Domain ===
 
''Topics may appear at multiple domains.''
 
''Topics may appear at multiple domains.''

Revision as of 16:47, 27 November 2006

Purpose

Coding standards are a part of defect prevention. They gather rules, advice and best practices for developing software, especially the code writing part. Here are listed some ideas what such standards could be for developing with C++ and within the OpenOffice.org project.

Identifying Rules

To make it easier to talk about the rules, each one gets an identifier. Because items can be added or sorted out, such ids should not be just cardinal numbers.

Here each rule belongs to a topic, which has an id, and has an id itself. Example: FDESIGN:OneTask is the rule with the id "OneTask" which belongs to the topic function design with the id FDESIGN.


Topics by Problem Domain

Topics may appear at multiple domains.

Middle- and Lowlevel Design

Classes

Functions and Implementation Generally

Preferred vs. Discarded Types and Habits

Files, Formatting, Documentation


Topics in Alphabetical Order


Personal tools