root/doc/latex/codingrules.tex @ 90

Revision 30, 3.1 kB (checked in by smidl, 17 years ago)

compiles and runs successfully, except KF_QR

  • Property svn:eol-style set to native
Line 
1\section{Coding Rules (Mostly inherited from IT++)}\label{codingrules}
2In the following sections we describe the naming conventions which are used for files, classes, structures, local variables, and global variables.\subsection{Default Naming Rules for Variables}\label{codingrules_cr_variables}
3Variables are named using lower-case letters and words are separated using under-score. Abbreviations, when used in variable names, are also written with lower-case letters. Examples:
4
5\begin{itemize}
6\item {\tt `fft\_\-size'}  \item {\tt `nrof\_\-paths'}  \item {\tt `my\_\-variable\_\-name'}  \end{itemize}
7
8
9Some variable names or parts of variable names are commonly used in several different functions and files to denote the same thing. For instance the following common names and prefixes should be used:
10
11\begin{itemize}
12\item {\tt `rows'} - number of rows in a matrix  \item {\tt `cols'} - number of columns in a matrix  \item {\tt `nrof\_\-'} - number of ...  \end{itemize}
13\subsection{Default Naming Rules for Files}\label{codingrules_cr_files}
14Files are named using lower-case letters and words are separated using under-score. Abbreviations, when used in file names, are also written with lower-case letters.
15
16Source files are named using {\tt `.cpp'} suffix, whereas header files end with {\tt `.h'} extension. Examples:
17
18\begin{itemize}
19\item {\tt `my\_\-file.h'}  \item {\tt `my\_\-file.cpp'}  \end{itemize}
20\subsection{Default Naming Rules for Functions}\label{codingrules_cr_functions}
21Function names are named using lower-case letters and words are separated using under-score. Abbreviations, when used in function names, are also written with lower-case letters. This rule applies both to stand-alone functions as well as to member functions of classes. Example:
22
23\begin{itemize}
24\item {\tt int my\_\-function\_\-name(int a, int b)}  \end{itemize}
25\subsection{Convention for sensitive functions}\label{codingrules_cr_specialfunctions}
26For efficiency, some functions may return pointers to internal variables. Such functionality is indicated by underscore as the first letter in the the name.
27
28\begin{itemize}
29\item {\tt mat$\ast$ \_\-internal\_\-matrix()}  \end{itemize}
30\subsection{Default Naming Rules for Classes and Structures}\label{codingrules_cr_classes}
31Each new word in a class or structure name should always start with a capital letter and the words should be separated with an under-score. Abbreviations are written with capital letters. Examples:
32
33\begin{itemize}
34\item {\tt `My\_\-Class\_\-Name'}  \item {\tt `My\_\-Struct\_\-Name'}  \item {\tt `OFDM'}  \end{itemize}
35\subsection{Default Functionality of Classes}\label{codingrules_cr_classes_functionality}
36All classes that are configured by input parameters should include:
37
38\begin{itemize}
39\item default empty constructor  \item one or more additional constructor(s) that takes input parameters and initializes the class instance  \item setup function, preferably named {\tt `setup'} or {\tt `set\_\-parameters'}  \end{itemize}
40
41
42Explicit destructor functions are not required, unless they are needed. It shall not be possible to use any of the other member functions unless the class has been properly initiated with the input parameters.
Note: See TracBrowser for help on using the browser.