Browse code

- doxygen configuration updated to the latest doxygen version

Jan Janak authored on 13/08/2007 12:37:39
Showing 1 changed files
... ...
@@ -1,17 +1,93 @@
1
+# Doxyfile 1.5.3
2
+
3
+# This file describes the settings to be used by the documentation system
4
+# doxygen (www.doxygen.org) for a project
5
+#
6
+# All text after a hash (#) is considered a comment and will be ignored
7
+# The format is:
8
+#       TAG = value [value, ...]
9
+# For lists items can also be appended using:
10
+#       TAG += value [value, ...]
11
+# Values that contain spaces should be placed between quotes (" ")
12
+
1 13
 #---------------------------------------------------------------------------
2 14
 # Project related configuration options
3 15
 #---------------------------------------------------------------------------
16
+
17
+# This tag specifies the encoding used for all characters in the config file that 
18
+# follow. The default is UTF-8 which is also the encoding used for all text before 
19
+# the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into 
20
+# libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of 
21
+# possible encodings.
22
+
23
+DOXYFILE_ENCODING      = UTF-8
24
+
25
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
26
+# by quotes) that should identify the project.
27
+
4 28
 PROJECT_NAME           = SER
29
+
30
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
31
+# This could be handy for archiving the generated documentation or 
32
+# if some version control system is used.
33
+
5 34
 PROJECT_NUMBER         = 2.0
6
-OUTPUT_DIRECTORY       = doc/doxygen/output
7
-CREATE_SUBDIRS         = YES
35
+
36
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
37
+# base path where the generated documentation will be put. 
38
+# If a relative path is entered, it will be relative to the location 
39
+# where doxygen was started. If left blank the current directory will be used.
40
+
41
+OUTPUT_DIRECTORY       = doc/doxygen/
42
+
43
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
44
+# 4096 sub-directories (in 2 levels) under the output directory of each output 
45
+# format and will distribute the generated files over these directories. 
46
+# Enabling this option can be useful when feeding doxygen a huge amount of 
47
+# source files, where putting all generated files in the same directory would 
48
+# otherwise cause performance problems for the file system.
49
+
50
+CREATE_SUBDIRS         = NO
51
+
52
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
53
+# documentation generated by doxygen is written. Doxygen will use this 
54
+# information to generate all constant output in the proper language. 
55
+# The default language is English, other supported languages are: 
56
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
57
+# Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, 
58
+# Italian, Japanese, Japanese-en (Japanese with English messages), Korean, 
59
+# Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, 
60
+# Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
61
+
8 62
 OUTPUT_LANGUAGE        = English
9
-USE_WINDOWS_ENCODING   = NO
63
+
64
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
65
+# include brief member descriptions after the members that are listed in 
66
+# the file and class documentation (similar to JavaDoc). 
67
+# Set to NO to disable this.
68
+
10 69
 BRIEF_MEMBER_DESC      = YES
11
-REPEAT_BRIEF           = YES
12
-ABBREVIATE_BRIEF       = "The $name class" \
13
-                         "The $name widget" \
14
-                         "The $name file" \
70
+
71
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
72
+# the brief description of a member or function before the detailed description. 
73
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
74
+# brief descriptions will be completely suppressed.
75
+
76
+REPEAT_BRIEF           = NO
77
+
78
+# This tag implements a quasi-intelligent brief description abbreviator 
79
+# that is used to form the text in various listings. Each string 
80
+# in this list, if found as the leading text of the brief description, will be 
81
+# stripped from the text and the result after processing the whole list, is 
82
+# used as the annotated text. Otherwise, the brief description is used as-is. 
83
+# If left blank, the following values are used ("$name" is automatically 
84
+# replaced with the name of the entity): "The $name class" "The $name widget" 
85
+# "The $name file" "is" "provides" "specifies" "contains" 
86
+# "represents" "a" "an" "the"
87
+
88
+ABBREVIATE_BRIEF       = "The $name class " \
89
+                         "The $name widget " \
90
+                         "The $name file " \
15 91
                          is \
16 92
                          provides \
17 93
                          specifies \
... ...
@@ -20,67 +96,413 @@ ABBREVIATE_BRIEF       = "The $name class" \
20 20
                          a \
21 21
                          an \
22 22
                          the
23
+
24
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
25
+# Doxygen will generate a detailed section even if there is only a brief 
26
+# description.
27
+
23 28
 ALWAYS_DETAILED_SEC    = NO
29
+
30
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
31
+# inherited members of a class in the documentation of that class as if those 
32
+# members were ordinary class members. Constructors, destructors and assignment 
33
+# operators of the base classes will not be shown.
34
+
24 35
 INLINE_INHERITED_MEMB  = NO
36
+
37
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
38
+# path before files name in the file list and in the header files. If set 
39
+# to NO the shortest path that makes the file name unique will be used.
40
+
25 41
 FULL_PATH_NAMES        = NO
42
+
43
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
44
+# can be used to strip a user-defined part of the path. Stripping is 
45
+# only done if one of the specified strings matches the left-hand part of 
46
+# the path. The tag can be used to show relative paths in the file list. 
47
+# If left blank the directory from which doxygen is run is used as the 
48
+# path to strip.
49
+
26 50
 STRIP_FROM_PATH        = 
51
+
52
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
53
+# the path mentioned in the documentation of a class, which tells 
54
+# the reader which header file to include in order to use a class. 
55
+# If left blank only the name of the header file containing the class 
56
+# definition is used. Otherwise one should specify the include paths that 
57
+# are normally passed to the compiler using the -I flag.
58
+
27 59
 STRIP_FROM_INC_PATH    = 
60
+
61
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
62
+# (but less readable) file names. This can be useful is your file systems 
63
+# doesn't support long names like on DOS, Mac, or CD-ROM.
64
+
28 65
 SHORT_NAMES            = NO
66
+
67
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
68
+# will interpret the first line (until the first dot) of a JavaDoc-style 
69
+# comment as the brief description. If set to NO, the JavaDoc 
70
+# comments will behave just like regular Qt-style comments 
71
+# (thus requiring an explicit @brief command for a brief description.)
72
+
29 73
 JAVADOC_AUTOBRIEF      = NO
74
+
75
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
76
+# interpret the first line (until the first dot) of a Qt-style 
77
+# comment as the brief description. If set to NO, the comments 
78
+# will behave just like regular Qt-style comments (thus requiring 
79
+# an explicit \brief command for a brief description.)
80
+
81
+QT_AUTOBRIEF           = NO
82
+
83
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
84
+# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
85
+# comments) as a brief description. This used to be the default behaviour. 
86
+# The new default is to treat a multi-line C++ comment block as a detailed 
87
+# description. Set this tag to YES if you prefer the old behaviour instead.
88
+
30 89
 MULTILINE_CPP_IS_BRIEF = NO
90
+
91
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen 
92
+# will output the detailed description near the top, like JavaDoc.
93
+# If set to NO, the detailed description appears after the member 
94
+# documentation.
95
+
31 96
 DETAILS_AT_TOP         = NO
97
+
98
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
99
+# member inherits the documentation from any documented member that it 
100
+# re-implements.
101
+
32 102
 INHERIT_DOCS           = YES
103
+
104
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
105
+# a new page for each member. If set to NO, the documentation of a member will 
106
+# be part of the file/class/namespace that contains it.
107
+
33 108
 SEPARATE_MEMBER_PAGES  = NO
109
+
110
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
111
+# Doxygen uses this value to replace tabs by spaces in code fragments.
112
+
34 113
 TAB_SIZE               = 8
114
+
115
+# This tag can be used to specify a number of aliases that acts 
116
+# as commands in the documentation. An alias has the form "name=value". 
117
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
118
+# put the command \sideeffect (or @sideeffect) in the documentation, which 
119
+# will result in a user-defined paragraph with heading "Side Effects:". 
120
+# You can put \n's in the value part of an alias to insert newlines.
121
+
35 122
 ALIASES                = 
123
+
124
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
125
+# sources only. Doxygen will then generate output that is more tailored for C. 
126
+# For instance, some of the names that are used will be different. The list 
127
+# of all members will be omitted, etc.
128
+
36 129
 OPTIMIZE_OUTPUT_FOR_C  = YES
130
+
131
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
132
+# sources only. Doxygen will then generate output that is more tailored for Java. 
133
+# For instance, namespaces will be presented as packages, qualified scopes 
134
+# will look different, etc.
135
+
37 136
 OPTIMIZE_OUTPUT_JAVA   = NO
137
+
138
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to 
139
+# include (a tag file for) the STL sources as input, then you should 
140
+# set this tag to YES in order to let doxygen match functions declarations and 
141
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
142
+# func(std::string) {}). This also make the inheritance and collaboration 
143
+# diagrams that involve STL classes more complete and accurate.
144
+
38 145
 BUILTIN_STL_SUPPORT    = NO
146
+
147
+# If you use Microsoft's C++/CLI language, you should set this option to YES to
148
+# enable parsing support.
149
+
150
+CPP_CLI_SUPPORT        = NO
151
+
152
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
153
+# tag is set to YES, then doxygen will reuse the documentation of the first 
154
+# member in the group (if any) for the other members of the group. By default 
155
+# all members of a group must be documented explicitly.
156
+
39 157
 DISTRIBUTE_GROUP_DOC   = NO
158
+
159
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
160
+# the same type (for instance a group of public functions) to be put as a 
161
+# subgroup of that type (e.g. under the Public Functions section). Set it to 
162
+# NO to prevent subgrouping. Alternatively, this can be done per class using 
163
+# the \nosubgrouping command.
164
+
40 165
 SUBGROUPING            = YES
166
+
41 167
 #---------------------------------------------------------------------------
42 168
 # Build related configuration options
43 169
 #---------------------------------------------------------------------------
170
+
171
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
172
+# documentation are documented, even if no documentation was available. 
173
+# Private class members and static file members will be hidden unless 
174
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
175
+
44 176
 EXTRACT_ALL            = NO
177
+
178
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
179
+# will be included in the documentation.
180
+
45 181
 EXTRACT_PRIVATE        = NO
46
-EXTRACT_STATIC         = NO
182
+
183
+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
184
+# will be included in the documentation.
185
+
186
+EXTRACT_STATIC         = YES
187
+
188
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
189
+# defined locally in source files will be included in the documentation. 
190
+# If set to NO only classes defined in header files are included.
191
+
47 192
 EXTRACT_LOCAL_CLASSES  = YES
193
+
194
+# This flag is only useful for Objective-C code. When set to YES local 
195
+# methods, which are defined in the implementation section but not in 
196
+# the interface are included in the documentation. 
197
+# If set to NO (the default) only methods in the interface are included.
198
+
48 199
 EXTRACT_LOCAL_METHODS  = NO
200
+
201
+# If this flag is set to YES, the members of anonymous namespaces will be extracted 
202
+# and appear in the documentation as a namespace called 'anonymous_namespace{file}', 
203
+# where file will be replaced with the base name of the file that contains the anonymous 
204
+# namespace. By default anonymous namespace are hidden.
205
+
206
+EXTRACT_ANON_NSPACES   = NO
207
+
208
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
209
+# undocumented members of documented classes, files or namespaces. 
210
+# If set to NO (the default) these members will be included in the 
211
+# various overviews, but no documentation section is generated. 
212
+# This option has no effect if EXTRACT_ALL is enabled.
213
+
49 214
 HIDE_UNDOC_MEMBERS     = YES
215
+
216
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
217
+# undocumented classes that are normally visible in the class hierarchy. 
218
+# If set to NO (the default) these classes will be included in the various 
219
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
220
+
50 221
 HIDE_UNDOC_CLASSES     = YES
222
+
223
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
224
+# friend (class|struct|union) declarations. 
225
+# If set to NO (the default) these declarations will be included in the 
226
+# documentation.
227
+
51 228
 HIDE_FRIEND_COMPOUNDS  = NO
229
+
230
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
231
+# documentation blocks found inside the body of a function. 
232
+# If set to NO (the default) these blocks will be appended to the 
233
+# function's detailed documentation block.
234
+
52 235
 HIDE_IN_BODY_DOCS      = NO
236
+
237
+# The INTERNAL_DOCS tag determines if documentation 
238
+# that is typed after a \internal command is included. If the tag is set 
239
+# to NO (the default) then the documentation will be excluded. 
240
+# Set it to YES to include the internal documentation.
241
+
53 242
 INTERNAL_DOCS          = NO
243
+
244
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
245
+# file names in lower-case letters. If set to YES upper-case letters are also 
246
+# allowed. This is useful if you have classes or files whose names only differ 
247
+# in case and if your file system supports case sensitive file names. Windows 
248
+# and Mac users are advised to set this option to NO.
249
+
54 250
 CASE_SENSE_NAMES       = YES
251
+
252
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
253
+# will show members with their full class and namespace scopes in the 
254
+# documentation. If set to YES the scope will be hidden.
255
+
55 256
 HIDE_SCOPE_NAMES       = NO
257
+
258
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
259
+# will put a list of the files that are included by a file in the documentation 
260
+# of that file.
261
+
56 262
 SHOW_INCLUDE_FILES     = YES
263
+
264
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
265
+# is inserted in the documentation for inline members.
266
+
57 267
 INLINE_INFO            = YES
268
+
269
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
270
+# will sort the (detailed) documentation of file and class members 
271
+# alphabetically by member name. If set to NO the members will appear in 
272
+# declaration order.
273
+
58 274
 SORT_MEMBER_DOCS       = YES
275
+
276
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
277
+# brief documentation of file, namespace and class members alphabetically 
278
+# by member name. If set to NO (the default) the members will appear in 
279
+# declaration order.
280
+
59 281
 SORT_BRIEF_DOCS        = NO
282
+
283
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
284
+# sorted by fully-qualified names, including namespaces. If set to 
285
+# NO (the default), the class list will be sorted only by class name, 
286
+# not including the namespace part. 
287
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
288
+# Note: This option applies only to the class list, not to the 
289
+# alphabetical list.
290
+
60 291
 SORT_BY_SCOPE_NAME     = NO
292
+
293
+# The GENERATE_TODOLIST tag can be used to enable (YES) or 
294
+# disable (NO) the todo list. This list is created by putting \todo 
295
+# commands in the documentation.
296
+
61 297
 GENERATE_TODOLIST      = YES
298
+
299
+# The GENERATE_TESTLIST tag can be used to enable (YES) or 
300
+# disable (NO) the test list. This list is created by putting \test 
301
+# commands in the documentation.
302
+
62 303
 GENERATE_TESTLIST      = YES
304
+
305
+# The GENERATE_BUGLIST tag can be used to enable (YES) or 
306
+# disable (NO) the bug list. This list is created by putting \bug 
307
+# commands in the documentation.
308
+
63 309
 GENERATE_BUGLIST       = YES
310
+
311
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
312
+# disable (NO) the deprecated list. This list is created by putting 
313
+# \deprecated commands in the documentation.
314
+
64 315
 GENERATE_DEPRECATEDLIST= YES
316
+
317
+# The ENABLED_SECTIONS tag can be used to enable conditional 
318
+# documentation sections, marked by \if sectionname ... \endif.
319
+
65 320
 ENABLED_SECTIONS       = 
321
+
322
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
323
+# the initial value of a variable or define consists of for it to appear in 
324
+# the documentation. If the initializer consists of more lines than specified 
325
+# here it will be hidden. Use a value of 0 to hide initializers completely. 
326
+# The appearance of the initializer of individual variables and defines in the 
327
+# documentation can be controlled using \showinitializer or \hideinitializer 
328
+# command in the documentation regardless of this setting.
329
+
66 330
 MAX_INITIALIZER_LINES  = 30
331
+
332
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
333
+# at the bottom of the documentation of classes and structs. If set to YES the 
334
+# list will mention the files that were used to generate the documentation.
335
+
67 336
 SHOW_USED_FILES        = YES
68
-SHOW_DIRECTORIES       = NO
69
-#FILE_VERSION_FILTER    = "/bin/sh doc/doxygen/versionfilter.sh"
337
+
338
+# If the sources in your project are distributed over multiple directories 
339
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
340
+# in the documentation. The default is NO.
341
+
342
+SHOW_DIRECTORIES       = YES
343
+
344
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
345
+# doxygen should invoke to get the current version for each file (typically from the 
346
+# version control system). Doxygen will invoke the program by executing (via 
347
+# popen()) the command <command> <input-file>, where <command> is the value of 
348
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
349
+# provided by doxygen. Whatever the program writes to standard output 
350
+# is used as the file version. See the manual for examples.
351
+
352
+FILE_VERSION_FILTER    = 
353
+
70 354
 #---------------------------------------------------------------------------
71 355
 # configuration options related to warning and progress messages
72 356
 #---------------------------------------------------------------------------
357
+
358
+# The QUIET tag can be used to turn on/off the messages that are generated 
359
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
360
+
73 361
 QUIET                  = NO
362
+
363
+# The WARNINGS tag can be used to turn on/off the warning messages that are 
364
+# generated by doxygen. Possible values are YES and NO. If left blank 
365
+# NO is used.
366
+
74 367
 WARNINGS               = YES
75
-WARN_IF_UNDOCUMENTED   = YES
368
+
369
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
370
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
371
+# automatically be disabled.
372
+
373
+WARN_IF_UNDOCUMENTED   = NO
374
+
375
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
376
+# potential errors in the documentation, such as not documenting some 
377
+# parameters in a documented function, or documenting parameters that 
378
+# don't exist or using markup commands wrongly.
379
+
76 380
 WARN_IF_DOC_ERROR      = YES
77
-WARN_NO_PARAMDOC       = NO
78
-WARN_FORMAT            = "$file:$line: $text"
381
+
382
+# This WARN_NO_PARAMDOC option can be abled to get warnings for 
383
+# functions that are documented, but have no documentation for their parameters 
384
+# or return value. If set to NO (the default) doxygen will only warn about 
385
+# wrong or incomplete parameter documentation, but not about the absence of 
386
+# documentation.
387
+
388
+WARN_NO_PARAMDOC       = YES
389
+
390
+# The WARN_FORMAT tag determines the format of the warning messages that 
391
+# doxygen can produce. The string should contain the $file, $line, and $text 
392
+# tags, which will be replaced by the file and line number from which the 
393
+# warning originated and the warning text. Optionally the format may contain 
394
+# $version, which will be replaced by the version of the file (if it could 
395
+# be obtained via FILE_VERSION_FILTER)
396
+
397
+WARN_FORMAT            = "$file:$line: $text "
398
+
399
+# The WARN_LOGFILE tag can be used to specify a file to which warning 
400
+# and error messages should be written. If left blank the output is written 
401
+# to stderr.
402
+
79 403
 WARN_LOGFILE           = 
404
+
80 405
 #---------------------------------------------------------------------------
81 406
 # configuration options related to the input files
82 407
 #---------------------------------------------------------------------------
408
+
409
+# The INPUT tag can be used to specify the files and/or directories that contain 
410
+# documented source files. You may enter file names like "myfile.cpp" or 
411
+# directories like "/usr/src/myproject". Separate the files or directories 
412
+# with spaces.
413
+
83 414
 INPUT                  = 
415
+
416
+# This tag can be used to specify the character encoding of the source files that 
417
+# doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default 
418
+# input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. 
419
+# See http://www.gnu.org/software/libiconv for the list of possible encodings.
420
+
421
+INPUT_ENCODING         = UTF-8
422
+
423
+# If the value of the INPUT tag contains directories, you can use the 
424
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
425
+# and *.h) to filter out the source-files in the directories. If left 
426
+# blank the following patterns are tested: 
427
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
428
+# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py
429
+
84 430
 FILE_PATTERNS          = *.c \
85 431
                          *.cc \
86 432
                          *.cxx \
... ...
@@ -104,157 +526,806 @@ FILE_PATTERNS          = *.c \
104 104
                          *.PHP \
105 105
                          *.PHP3 \
106 106
                          *.PY
107
+
108
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
109
+# should be searched for input files as well. Possible values are YES and NO. 
110
+# If left blank NO is used.
111
+
107 112
 RECURSIVE              = YES
108
-EXCLUDE                =
113
+
114
+# The EXCLUDE tag can be used to specify files and/or directories that should 
115
+# excluded from the INPUT source files. This way you can easily exclude a 
116
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
117
+
118
+EXCLUDE                = 
119
+
120
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
121
+# directories that are symbolic links (a Unix filesystem feature) are excluded 
122
+# from the input.
123
+
109 124
 EXCLUDE_SYMLINKS       = NO
125
+
126
+# If the value of the INPUT tag contains directories, you can use the 
127
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
128
+# certain files from those directories. Note that the wildcards are matched 
129
+# against the file with absolute path, so to exclude all test directories 
130
+# for example use the pattern */test/*
131
+
110 132
 EXCLUDE_PATTERNS       = */CVS/* \
111
-			 */etc/* \
112
-			 */examples/* \
113
-			 */pkg/* \
114
-			 */profile/* \
115
-			 */scripts/*
133
+                         */etc/* \
134
+                         */examples/* \
135
+                         */pkg/* \
136
+                         */profile/* \
137
+                         */scripts/*
138
+
139
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
140
+# (namespaces, classes, functions, etc.) that should be excluded from the output. 
141
+# The symbol name can be a fully qualified name, a word, or if the wildcard * is used, 
142
+# a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test
143
+
144
+EXCLUDE_SYMBOLS        = 
145
+
146
+# The EXAMPLE_PATH tag can be used to specify one or more files or 
147
+# directories that contain example code fragments that are included (see 
148
+# the \include command).
149
+
116 150
 EXAMPLE_PATH           = doc/doxygen/examples
151
+
152
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
153
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
154
+# and *.h) to filter out the source-files in the directories. If left 
155
+# blank all files are included.
156
+
117 157
 EXAMPLE_PATTERNS       = *
158
+
159
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
160
+# searched for input files to be used with the \include or \dontinclude 
161
+# commands irrespective of the value of the RECURSIVE tag. 
162
+# Possible values are YES and NO. If left blank NO is used.
163
+
118 164
 EXAMPLE_RECURSIVE      = YES
165
+
166
+# The IMAGE_PATH tag can be used to specify one or more files or 
167
+# directories that contain image that are included in the documentation (see 
168
+# the \image command).
169
+
119 170
 IMAGE_PATH             = 
171
+
172
+# The INPUT_FILTER tag can be used to specify a program that doxygen should 
173
+# invoke to filter for each input file. Doxygen will invoke the filter program 
174
+# by executing (via popen()) the command <filter> <input-file>, where <filter> 
175
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
176
+# input file. Doxygen will then use the output that the filter program writes 
177
+# to standard output.  If FILTER_PATTERNS is specified, this tag will be 
178
+# ignored.
179
+
120 180
 INPUT_FILTER           = 
181
+
182
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
183
+# basis.  Doxygen will compare the file name with each pattern and apply the 
184
+# filter if there is a match.  The filters are a list of the form: 
185
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
186
+# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
187
+# is applied to all files.
188
+
121 189
 FILTER_PATTERNS        = 
190
+
191
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
192
+# INPUT_FILTER) will be used to filter the input files when producing source 
193
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
194
+
122 195
 FILTER_SOURCE_FILES    = NO
196
+
123 197
 #---------------------------------------------------------------------------
124 198
 # configuration options related to source browsing
125 199
 #---------------------------------------------------------------------------
200
+
201
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
202
+# be generated. Documented entities will be cross-referenced with these sources. 
203
+# Note: To get rid of all source code in the generated output, make sure also 
204
+# VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH 
205
+# then you must also enable this option. If you don't then doxygen will produce 
206
+# a warning and turn it on anyway
207
+
126 208
 SOURCE_BROWSER         = YES
209
+
210
+# Setting the INLINE_SOURCES tag to YES will include the body 
211
+# of functions and classes directly in the documentation.
212
+
127 213
 INLINE_SOURCES         = NO
214
+
215
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
216
+# doxygen to hide any special comment blocks from generated source code 
217
+# fragments. Normal C and C++ comments will always remain visible.
218
+
128 219
 STRIP_CODE_COMMENTS    = YES
220
+
221
+# If the REFERENCED_BY_RELATION tag is set to YES (the default) 
222
+# then for each documented function all documented 
223
+# functions referencing it will be listed.
224
+
129 225
 REFERENCED_BY_RELATION = YES
226
+
227
+# If the REFERENCES_RELATION tag is set to YES (the default) 
228
+# then for each documented function all documented entities 
229
+# called/used by that function will be listed.
230
+
130 231
 REFERENCES_RELATION    = YES
232
+
233
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
234
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
235
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
236
+# link to the source code.  Otherwise they will link to the documentstion.
237
+
131 238
 REFERENCES_LINK_SOURCE = YES
239
+
240
+# If the USE_HTAGS tag is set to YES then the references to source code 
241
+# will point to the HTML generated by the htags(1) tool instead of doxygen 
242
+# built-in source browser. The htags tool is part of GNU's global source 
243
+# tagging system (see http://www.gnu.org/software/global/global.html). You 
244
+# will need version 4.8.6 or higher.
245
+
132 246
 USE_HTAGS              = NO
247
+
248
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
249
+# will generate a verbatim copy of the header file for each class for 
250
+# which an include is specified. Set to NO to disable this.
251
+
133 252
 VERBATIM_HEADERS       = YES
253
+
134 254
 #---------------------------------------------------------------------------
135 255
 # configuration options related to the alphabetical class index
136 256
 #---------------------------------------------------------------------------
257
+
258
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
259
+# of all compounds will be generated. Enable this if the project 
260
+# contains a lot of classes, structs, unions or interfaces.
261
+
137 262
 ALPHABETICAL_INDEX     = YES
263
+
264
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
265
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
266
+# in which this list will be split (can be a number in the range [1..20])
267
+
138 268
 COLS_IN_ALPHA_INDEX    = 5
269
+
270
+# In case all classes in a project start with a common prefix, all 
271
+# classes will be put under the same header in the alphabetical index. 
272
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
273
+# should be ignored while generating the index headers.
274
+
139 275
 IGNORE_PREFIX          = 
276
+
140 277
 #---------------------------------------------------------------------------
141 278
 # configuration options related to the HTML output
142 279
 #---------------------------------------------------------------------------
280
+
281
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
282
+# generate HTML output.
283
+
143 284
 GENERATE_HTML          = YES
285
+
286
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
287
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
288
+# put in front of it. If left blank `html' will be used as the default path.
289
+
144 290
 HTML_OUTPUT            = html
291
+
292
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
293
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
294
+# doxygen will generate files with .html extension.
295
+
145 296
 HTML_FILE_EXTENSION    = .html
297
+
298
+# The HTML_HEADER tag can be used to specify a personal HTML header for 
299
+# each generated HTML page. If it is left blank doxygen will generate a 
300
+# standard header.
301
+
146 302
 HTML_HEADER            = 
303
+
304
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
305
+# each generated HTML page. If it is left blank doxygen will generate a 
306
+# standard footer.
307
+
147 308
 HTML_FOOTER            = 
309
+
310
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
311
+# style sheet that is used by each HTML page. It can be used to 
312
+# fine-tune the look of the HTML output. If the tag is left blank doxygen 
313
+# will generate a default style sheet. Note that doxygen will try to copy 
314
+# the style sheet file to the HTML output directory, so don't put your own 
315
+# stylesheet in the HTML output directory as well, or it will be erased!
316
+
148 317
 HTML_STYLESHEET        = 
318
+
319
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
320
+# files or namespaces will be aligned in HTML using tables. If set to 
321
+# NO a bullet list will be used.
322
+
149 323
 HTML_ALIGN_MEMBERS     = YES
324
+
325
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
326
+# will be generated that can be used as input for tools like the 
327
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
328
+# of the generated HTML documentation.
329
+
150 330
 GENERATE_HTMLHELP      = NO
331
+
332
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
333
+# documentation will contain sections that can be hidden and shown after the 
334
+# page has loaded. For this to work a browser that supports 
335
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 
336
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
337
+
338
+HTML_DYNAMIC_SECTIONS  = NO
339
+
340
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
341
+# be used to specify the file name of the resulting .chm file. You 
342
+# can add a path in front of the file if the result should not be 
343
+# written to the html output directory.
344
+
151 345
 CHM_FILE               = 
346
+
347
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
348
+# be used to specify the location (absolute path including file name) of 
349
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
350
+# the HTML help compiler on the generated index.hhp.
351
+
152 352
 HHC_LOCATION           = 
353
+
354
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
355
+# controls if a separate .chi index file is generated (YES) or that 
356
+# it should be included in the master .chm file (NO).
357
+
153 358
 GENERATE_CHI           = NO
359
+
360
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
361
+# controls whether a binary table of contents is generated (YES) or a 
362
+# normal table of contents (NO) in the .chm file.
363
+
154 364
 BINARY_TOC             = NO
365
+
366
+# The TOC_EXPAND flag can be set to YES to add extra items for group members 
367
+# to the contents of the HTML help documentation and to the tree view.
368
+
155 369
 TOC_EXPAND             = YES
370
+
371
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
372
+# top of each HTML page. The value NO (the default) enables the index and 
373
+# the value YES disables it.
374
+
156 375
 DISABLE_INDEX          = NO
376
+
377
+# This tag can be used to set the number of enum values (range [1..20]) 
378
+# that doxygen will group on one line in the generated HTML documentation.
379
+
157 380
 ENUM_VALUES_PER_LINE   = 4
381
+
382
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
383
+# generated containing a tree-like index structure (just like the one that 
384
+# is generated for HTML Help). For this to work a browser that supports 
385
+# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 
386
+# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 
387
+# probably better off using the HTML help feature.
388
+
158 389
 GENERATE_TREEVIEW      = no
390
+
391
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
392
+# used to set the initial width (in pixels) of the frame in which the tree 
393
+# is shown.
394
+
159 395
 TREEVIEW_WIDTH         = 250
396
+
160 397
 #---------------------------------------------------------------------------
161 398
 # configuration options related to the LaTeX output
162 399
 #---------------------------------------------------------------------------
400
+
401
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
402
+# generate Latex output.
403
+
163 404
 GENERATE_LATEX         = NO
405
+
406
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
407
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
408
+# put in front of it. If left blank `latex' will be used as the default path.
409
+
164 410
 LATEX_OUTPUT           = latex
411
+
412
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
413
+# invoked. If left blank `latex' will be used as the default command name.
414
+
165 415
 LATEX_CMD_NAME         = latex
416
+
417
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
418
+# generate index for LaTeX. If left blank `makeindex' will be used as the 
419
+# default command name.
420
+
166 421
 MAKEINDEX_CMD_NAME     = makeindex
422
+
423
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
424
+# LaTeX documents. This may be useful for small projects and may help to 
425
+# save some trees in general.
426
+
167 427
 COMPACT_LATEX          = NO
428
+
429
+# The PAPER_TYPE tag can be used to set the paper type that is used 
430
+# by the printer. Possible values are: a4, a4wide, letter, legal and 
431
+# executive. If left blank a4wide will be used.
432
+
168 433
 PAPER_TYPE             = a4wide
434
+
435
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
436
+# packages that should be included in the LaTeX output.
437
+
169 438
 EXTRA_PACKAGES         = 
439
+
440
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
441
+# the generated latex document. The header should contain everything until 
442
+# the first chapter. If it is left blank doxygen will generate a 
443
+# standard header. Notice: only use this tag if you know what you are doing!
444
+
170 445
 LATEX_HEADER           = 
446
+
447
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
448
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
449
+# contain links (just like the HTML output) instead of page references 
450
+# This makes the output suitable for online browsing using a pdf viewer.
451
+
171 452
 PDF_HYPERLINKS         = NO
453
+
454
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
455
+# plain latex in the generated Makefile. Set this option to YES to get a 
456
+# higher quality PDF documentation.
457
+
172 458
 USE_PDFLATEX           = NO
459
+
460
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
461
+# command to the generated LaTeX files. This will instruct LaTeX to keep 
462
+# running if errors occur, instead of asking the user for help. 
463
+# This option is also used when generating formulas in HTML.
464
+
173 465
 LATEX_BATCHMODE        = NO
466
+
467
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
468
+# include the index chapters (such as File Index, Compound Index, etc.) 
469
+# in the output.
470
+
174 471
 LATEX_HIDE_INDICES     = NO
472
+
175 473
 #---------------------------------------------------------------------------
176 474
 # configuration options related to the RTF output
177 475
 #---------------------------------------------------------------------------
476
+
477
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
478
+# The RTF output is optimized for Word 97 and may not look very pretty with 
479
+# other RTF readers or editors.
480
+
178 481
 GENERATE_RTF           = NO
482
+
483
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
484
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
485
+# put in front of it. If left blank `rtf' will be used as the default path.
486
+
179 487
 RTF_OUTPUT             = rtf
488
+
489
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
490
+# RTF documents. This may be useful for small projects and may help to 
491
+# save some trees in general.
492
+
180 493
 COMPACT_RTF            = NO
494
+
495
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
496
+# will contain hyperlink fields. The RTF file will 
497
+# contain links (just like the HTML output) instead of page references. 
498
+# This makes the output suitable for online browsing using WORD or other 
499
+# programs which support those fields. 
500
+# Note: wordpad (write) and others do not support links.
501
+
181 502
 RTF_HYPERLINKS         = NO
503
+
504
+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
505
+# config file, i.e. a series of assignments. You only have to provide 
506
+# replacements, missing definitions are set to their default value.
507
+
182 508
 RTF_STYLESHEET_FILE    = 
509
+
510
+# Set optional variables used in the generation of an rtf document. 
511
+# Syntax is similar to doxygen's config file.
512
+
183 513
 RTF_EXTENSIONS_FILE    = 
514
+
184 515
 #---------------------------------------------------------------------------
185 516
 # configuration options related to the man page output
186 517
 #---------------------------------------------------------------------------
518
+
519
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
520
+# generate man pages
521
+
187 522
 GENERATE_MAN           = NO
523
+
524
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
525
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
526
+# put in front of it. If left blank `man' will be used as the default path.
527
+
188 528
 MAN_OUTPUT             = man
529
+
530
+# The MAN_EXTENSION tag determines the extension that is added to 
531
+# the generated man pages (default is the subroutine's section .3)
532
+
189 533
 MAN_EXTENSION          = .3
534
+
535
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
536
+# then it will generate one additional man file for each entity 
537
+# documented in the real man page(s). These additional files 
538
+# only source the real man page, but without them the man command 
539
+# would be unable to find the correct page. The default is NO.
540
+
190 541
 MAN_LINKS              = NO
542
+
191 543
 #---------------------------------------------------------------------------
192 544
 # configuration options related to the XML output
193 545
 #---------------------------------------------------------------------------
546
+
547
+# If the GENERATE_XML tag is set to YES Doxygen will 
548
+# generate an XML file that captures the structure of 
549
+# the code including all documentation.
550
+
194 551
 GENERATE_XML           = NO
552
+
553
+# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
554
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
555
+# put in front of it. If left blank `xml' will be used as the default path.
556
+
195 557
 XML_OUTPUT             = xml
558
+
559
+# The XML_SCHEMA tag can be used to specify an XML schema, 
560
+# which can be used by a validating XML parser to check the 
561
+# syntax of the XML files.
562
+
196 563
 XML_SCHEMA             = 
564
+
565
+# The XML_DTD tag can be used to specify an XML DTD, 
566
+# which can be used by a validating XML parser to check the 
567
+# syntax of the XML files.
568
+
197 569
 XML_DTD                = 
570
+
571
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
572
+# dump the program listings (including syntax highlighting 
573
+# and cross-referencing information) to the XML output. Note that 
574
+# enabling this will significantly increase the size of the XML output.
575
+
198 576
 XML_PROGRAMLISTING     = YES
577
+
199 578
 #---------------------------------------------------------------------------
200 579
 # configuration options for the AutoGen Definitions output
201 580
 #---------------------------------------------------------------------------
581
+
582
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
583
+# generate an AutoGen Definitions (see autogen.sf.net) file 
584
+# that captures the structure of the code including all 
585
+# documentation. Note that this feature is still experimental 
586
+# and incomplete at the moment.
587
+
202 588
 GENERATE_AUTOGEN_DEF   = NO
589
+
203 590
 #---------------------------------------------------------------------------
204 591
 # configuration options related to the Perl module output
205 592
 #---------------------------------------------------------------------------
593
+
594
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
595
+# generate a Perl module file that captures the structure of 
596
+# the code including all documentation. Note that this 
597
+# feature is still experimental and incomplete at the 
598
+# moment.
599
+
206 600
 GENERATE_PERLMOD       = NO
601
+
602
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
603
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
604
+# to generate PDF and DVI output from the Perl module output.
605
+
207 606
 PERLMOD_LATEX          = NO
607
+
608
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
609
+# nicely formatted so it can be parsed by a human reader.  This is useful 
610
+# if you want to understand what is going on.  On the other hand, if this 
611
+# tag is set to NO the size of the Perl module output will be much smaller 
612
+# and Perl will parse it just the same.
613
+
208 614
 PERLMOD_PRETTY         = YES
615
+
616
+# The names of the make variables in the generated doxyrules.make file 
617
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
618
+# This is useful so different doxyrules.make files included by the same 
619
+# Makefile don't overwrite each other's variables.
620
+
209 621
 PERLMOD_MAKEVAR_PREFIX = 
622
+
210 623
 #---------------------------------------------------------------------------
211 624
 # Configuration options related to the preprocessor   
212 625
 #---------------------------------------------------------------------------
626
+
627
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
628
+# evaluate all C-preprocessor directives found in the sources and include 
629
+# files.
630
+
213 631
 ENABLE_PREPROCESSING   = YES
632
+
633
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
634
+# names in the source code. If set to NO (the default) only conditional 
635
+# compilation will be performed. Macro expansion can be done in a controlled 
636
+# way by setting EXPAND_ONLY_PREDEF to YES.
637
+
214 638
 MACRO_EXPANSION        = NO
639
+
640
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
641
+# then the macro expansion is limited to the macros specified with the 
642
+# PREDEFINED and EXPAND_AS_DEFINED tags.
643
+
215 644
 EXPAND_ONLY_PREDEF     = NO
645
+
646
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
647
+# in the INCLUDE_PATH (see below) will be search if a #include is found.
648
+
216 649
 SEARCH_INCLUDES        = YES
650
+
651
+# The INCLUDE_PATH tag can be used to specify one or more directories that 
652
+# contain include files that are not input files but should be processed by 
653
+# the preprocessor.
654
+
217 655
 INCLUDE_PATH           = 
656
+
657
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
658
+# patterns (like *.h and *.hpp) to filter out the header-files in the 
659
+# directories. If left blank, the patterns specified with FILE_PATTERNS will 
660
+# be used.
661
+
218 662
 INCLUDE_FILE_PATTERNS  = 
663
+
664
+# The PREDEFINED tag can be used to specify one or more macro names that 
665
+# are defined before the preprocessor is started (similar to the -D option of 
666
+# gcc). The argument of the tag is a list of macros of the form: name 
667
+# or name=definition (no spaces). If the definition and the = are 
668
+# omitted =1 is assumed. To prevent a macro definition from being 
669
+# undefined via #undef or recursively expanded use the := operator 
670
+# instead of the = operator.
671
+
219 672
 PREDEFINED             = 
673
+
674
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
675
+# this tag can be used to specify a list of macro names that should be expanded. 
676
+# The macro definition that is found in the sources will be used. 
677
+# Use the PREDEFINED tag if you want to use a different macro definition.
678
+
220 679
 EXPAND_AS_DEFINED      = 
680
+
681
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
682
+# doxygen's preprocessor will remove all function-like macros that are alone 
683
+# on a line, have an all uppercase name, and do not end with a semicolon. Such 
684
+# function macros are typically used for boiler-plate code, and will confuse 
685
+# the parser if not removed.
686
+
221 687
 SKIP_FUNCTION_MACROS   = YES
688
+
222 689
 #---------------------------------------------------------------------------
223 690
 # Configuration::additions related to external references   
224 691
 #---------------------------------------------------------------------------
692
+
693
+# The TAGFILES option can be used to specify one or more tagfiles. 
694
+# Optionally an initial location of the external documentation 
695
+# can be added for each tagfile. The format of a tag file without 
696
+# this location is as follows: 
697
+#   TAGFILES = file1 file2 ... 
698
+# Adding location for the tag files is done as follows: 
699
+#   TAGFILES = file1=loc1 "file2 = loc2" ... 
700
+# where "loc1" and "loc2" can be relative or absolute paths or 
701
+# URLs. If a location is present for each tag, the installdox tool 
702
+# does not have to be run to correct the links.
703
+# Note that each tag file must have a unique name
704
+# (where the name does NOT include the path)
705
+# If a tag file is not located in the directory in which doxygen 
706
+# is run, you must also specify the path to the tagfile here.
707
+
225 708
 TAGFILES               = 
709
+
710
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
711
+# a tag file that is based on the input files it reads.
712
+
226 713
 GENERATE_TAGFILE       = 
714
+
715
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
716
+# in the class index. If set to NO only the inherited external classes 
717
+# will be listed.
718
+
227 719
 ALLEXTERNALS           = NO
720
+
721
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
722
+# in the modules index. If set to NO, only the current project's groups will 
723
+# be listed.
724
+
228 725
 EXTERNAL_GROUPS        = YES
726
+
727
+# The PERL_PATH should be the absolute path and name of the perl script 
728
+# interpreter (i.e. the result of `which perl').
729
+
229 730
 PERL_PATH              = /usr/bin/perl
731
+
230 732
 #---------------------------------------------------------------------------
231 733
 # Configuration options related to the dot tool   
232 734
 #---------------------------------------------------------------------------
735
+
736
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
737
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
738
+# or super classes. Setting the tag to NO turns the diagrams off. Note that 
739
+# this option is superseded by the HAVE_DOT option below. This is only a 
740
+# fallback. It is recommended to install and use dot, since it yields more 
741
+# powerful graphs.
742
+
233 743
 CLASS_DIAGRAMS         = NO
744
+
745
+# You can define message sequence charts within doxygen comments using the \msc 
746
+# command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to 
747
+# produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to 
748
+# specify the directory where the mscgen tool resides. If left empty the tool is assumed to 
749
+# be found in the default search path.
750
+
751
+MSCGEN_PATH            = 
752
+
753
+# If set to YES, the inheritance and collaboration graphs will hide 
754
+# inheritance and usage relations if the target is undocumented 
755
+# or is not a class.
756
+
234 757
 HIDE_UNDOC_RELATIONS   = YES
758
+
759
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
760
+# available from the path. This tool is part of Graphviz, a graph visualization 
761
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
762
+# have no effect if this option is set to NO (the default)
763
+
235 764
 HAVE_DOT               = YES
765
+
766
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
767
+# will generate a graph for each documented class showing the direct and 
768
+# indirect inheritance relations. Setting this tag to YES will force the 
769
+# the CLASS_DIAGRAMS tag to NO.
770
+
236 771
 CLASS_GRAPH            = YES
772
+
773
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
774
+# will generate a graph for each documented class showing the direct and 
775
+# indirect implementation dependencies (inheritance, containment, and 
776
+# class references variables) of the class with other documented classes.
777
+
237 778
 COLLABORATION_GRAPH    = YES
779
+
780
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
781
+# will generate a graph for groups, showing the direct groups dependencies
782
+
238 783
 GROUP_GRAPHS           = YES
784
+
785
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
786
+# collaboration diagrams in a style similar to the OMG's Unified Modeling 
787
+# Language.
788
+
239 789
 UML_LOOK               = NO
790
+
791
+# If set to YES, the inheritance and collaboration graphs will show the 
792
+# relations between templates and their instances.
793
+
240 794
 TEMPLATE_RELATIONS     = NO
795
+
796
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
797
+# tags are set to YES then doxygen will generate a graph for each documented 
798
+# file showing the direct and indirect include dependencies of the file with 
799
+# other documented files.
800
+
241 801
 INCLUDE_GRAPH          = YES
802
+
803
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
804
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
805
+# documented header file showing the documented files that directly or 
806
+# indirectly include this file.
807
+
242 808
 INCLUDED_BY_GRAPH      = YES
809
+
810
+# If the CALL_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 
811
+# generate a call dependency graph for every global function or class method. 
812
+# Note that enabling this option will significantly increase the time of a run. 
813
+# So in most cases it will be better to enable call graphs for selected 
814
+# functions only using the \callgraph command.
815
+
243 816
 CALL_GRAPH             = YES
817
+
818
+# If the CALLER_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 
819
+# generate a caller dependency graph for every global function or class method. 
820
+# Note that enabling this option will significantly increase the time of a run. 
821
+# So in most cases it will be better to enable caller graphs for selected 
822
+# functions only using the \callergraph command.
823
+
244 824
 CALLER_GRAPH           = YES
825
+
826
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
827
+# will graphical hierarchy of all classes instead of a textual one.
828
+
245 829
 GRAPHICAL_HIERARCHY    = YES
830
+
831
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
832
+# then doxygen will show the dependencies a directory has on other directories 
833
+# in a graphical way. The dependency relations are determined by the #include
834
+# relations between the files in the directories.
835
+
246 836
 DIRECTORY_GRAPH        = YES
837
+
838
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
839
+# generated by dot. Possible values are png, jpg, or gif
840
+# If left blank png will be used.
841
+
247 842
 DOT_IMAGE_FORMAT       = png
843
+
844
+# The tag DOT_PATH can be used to specify the path where the dot tool can be 
845
+# found. If left blank, it is assumed the dot tool can be found in the path.
846
+
248 847
 DOT_PATH               = 
848
+
849
+# The DOTFILE_DIRS tag can be used to specify one or more directories that 
850
+# contain dot files that are included in the documentation (see the 
851
+# \dotfile command).
852
+
249 853
 DOTFILE_DIRS           = 
250
-MAX_DOT_GRAPH_WIDTH    = 1024
251
-MAX_DOT_GRAPH_HEIGHT   = 1024
854
+
855
+# The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 
856
+# nodes that will be shown in the graph. If the number of nodes in a graph 
857
+# becomes larger than this value, doxygen will truncate the graph, which is 
858
+# visualized by representing a node as a red box. Note that doxygen if the number 
859
+# of direct children of the root node in a graph is already larger than 
860
+# MAX_DOT_GRAPH_NOTES then the graph will not be shown at all. Also note 
861
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
862
+
863
+DOT_GRAPH_MAX_NODES    = 50
864
+
865
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
866
+# graphs generated by dot. A depth value of 3 means that only nodes reachable 
867
+# from the root by following a path via at most 3 edges will be shown. Nodes 
868
+# that lay further from the root node will be omitted. Note that setting this 
869
+# option to 1 or 2 may greatly reduce the computation time needed for large 
870
+# code bases. Also note that the size of a graph can be further restricted by 
871
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
872
+
252 873
 MAX_DOT_GRAPH_DEPTH    = 1000
874
+
875
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
876
+# background. This is disabled by default, which results in a white background. 
877
+# Warning: Depending on the platform used, enabling this option may lead to 
878
+# badly anti-aliased labels on the edges of a graph (i.e. they become hard to 
879
+# read).
880
+
253 881
 DOT_TRANSPARENT        = NO
882
+
883
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
884
+# files in one run (i.e. multiple -o and -T options on the command line). This 
885
+# makes dot run faster, but since only newer versions of dot (>1.8.10) 
886
+# support this, this feature is disabled by default.
887
+
254 888
 DOT_MULTI_TARGETS      = NO
889
+
890
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
891
+# generate a legend page explaining the meaning of the various boxes and 
892
+# arrows in the dot generated graphs.
893
+
255 894
 GENERATE_LEGEND        = YES
895
+
896
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
897
+# remove the intermediate dot files that are used to generate 
898
+# the various graphs.
899
+
256 900
 DOT_CLEANUP            = YES
901
+
257 902
 #---------------------------------------------------------------------------
258 903
 # Configuration::additions related to the search engine   
259 904
 #---------------------------------------------------------------------------
905
+
906
+# The SEARCHENGINE tag specifies whether or not a search engine should be 
907
+# used. If set to NO the values of all tags below this one will be ignored.
908
+
260 909
 SEARCHENGINE           = NO