1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
/*!
\page documentation Documentation Rules
\section doc_general General Rules
All classes in IT++ should be properly documented with Doxygen
comments in include (`.h') files. Source (`.cpp') files should be
documented according to a normal standard for well documented C++
code.
An example of how the interface of a class shall be documented in IT++
is shown here:
\verbatim
/*!
* \brief Brief description of My_Class here
*
* Detailed description of My_Class here. With example code if needed.
*/
class My_Class {
public:
//! Default constructor
My_Class(void) { setup_done = false; }
/*!
* \brief Constructor that initializes the class with parameters
*
* Detailed description of the constructor here if needed
*
* \param[in] param1 Description of \a param1 here
* \param[in] param2 Description of \a param2 here
*/
My_Class(TYPE1 param1, TYPE2 param2) { setup(param1, param2); }
/*!
* \brief Setup function for My_Class
*
* Detailed description of the setup function here if needed
*
* \param[in] param1 Description of \a param1 here
* \param[in] param2 Description of \a param2 here
*/
void setup(TYPE1 param1, TYPE2 param2);
/*!
* \brief Brief description of member_function1
*
* Detailed description of member_function1 here if needed
*
* \param[in] param1 Description of \a param1 here
* \param[in] param2 Description of \a param2 here
* \param[in,out] param3 Description of \a param3 here
* \return Description of the return value here
*/
TYPE4 member_function1(TYPE1 param1, TYPE2 param2, TYPE3 ¶m3);
private:
bool setup_done; /*!< Variable that checks if the class is properly
initialized with parameters */
TYPE1 private_variable1; //!< Short description of private_variable1 here
TYPE2 private_variable2; //!< Short description of private_variable2 here
};
\endverbatim
\section doc_header File Header
All files should start with the following header, which include Doxygen's \c
\\file, \c \\brief and \c \\author tags, and a common copyright note:
\verbatim
/*!
* \file
* \brief Brief description of the file here
* \author Names of the authors who contributed to this code
*
* Detailed description of the file here if needed.
*
* -------------------------------------------------------------------------
*
* IT++ - C++ library of mathematical, signal processing, speech processing,
* and communications classes and functions
*
* Copyright (C) 1995-2005 (see AUTHORS file for a list of contributors)
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*
* -------------------------------------------------------------------------
*/
\endverbatim
\section doc_groups Grouping Various Parts
All functions must be added to a Doxygen group in order to appear in
the documentation. The following code example defines the group \c
`my_group':
\verbatim
/*!
* \defgroup my_group Brief description of the group here
*
* Detailed description of the group here
*/
\endverbatim
The following example shows how to document the function \c
`my_function' and how to add it to the group \c `my_group':
\verbatim
/*!
* \brief Brief description of my_function here
* \ingroup my_group
*
* Detailed description of my_function here
*
* \param[in] param1 Description of \a param1 here
* \param[in] param2 Description of \a param2 here
* \return Description of the return value here
*/
TYPE3 my_function(TYPE1 param1, TYPE2 ¶m2);
\endverbatim
*/
|
