include/doxyfile
branchSDL-1.3
changeset 1662 782fd950bd46
child 5067 61d53410eb41
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/include/doxyfile	Sun May 28 13:04:16 2006 +0000
     1.3 @@ -0,0 +1,1229 @@
     1.4 +# Doxyfile 1.4.4
     1.5 +
     1.6 +# This file describes the settings to be used by the documentation system
     1.7 +# doxygen (www.doxygen.org) for a project
     1.8 +#
     1.9 +# All text after a hash (#) is considered a comment and will be ignored
    1.10 +# The format is:
    1.11 +#       TAG = value [value, ...]
    1.12 +# For lists items can also be appended using:
    1.13 +#       TAG += value [value, ...]
    1.14 +# Values that contain spaces should be placed between quotes (" ")
    1.15 +
    1.16 +#---------------------------------------------------------------------------
    1.17 +# Project related configuration options
    1.18 +#---------------------------------------------------------------------------
    1.19 +
    1.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
    1.21 +# by quotes) that should identify the project.
    1.22 +
    1.23 +PROJECT_NAME           = SDL
    1.24 +
    1.25 +# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
    1.26 +# This could be handy for archiving the generated documentation or 
    1.27 +# if some version control system is used.
    1.28 +
    1.29 +PROJECT_NUMBER         = 1.3.0
    1.30 +
    1.31 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
    1.32 +# base path where the generated documentation will be put. 
    1.33 +# If a relative path is entered, it will be relative to the location 
    1.34 +# where doxygen was started. If left blank the current directory will be used.
    1.35 +
    1.36 +OUTPUT_DIRECTORY       = docs
    1.37 +
    1.38 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
    1.39 +# 4096 sub-directories (in 2 levels) under the output directory of each output 
    1.40 +# format and will distribute the generated files over these directories. 
    1.41 +# Enabling this option can be useful when feeding doxygen a huge amount of 
    1.42 +# source files, where putting all generated files in the same directory would 
    1.43 +# otherwise cause performance problems for the file system.
    1.44 +
    1.45 +CREATE_SUBDIRS         = NO
    1.46 +
    1.47 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    1.48 +# documentation generated by doxygen is written. Doxygen will use this 
    1.49 +# information to generate all constant output in the proper language. 
    1.50 +# The default language is English, other supported languages are: 
    1.51 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, 
    1.52 +# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese, 
    1.53 +# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian, 
    1.54 +# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, 
    1.55 +# Swedish, and Ukrainian.
    1.56 +
    1.57 +OUTPUT_LANGUAGE        = English
    1.58 +
    1.59 +# This tag can be used to specify the encoding used in the generated output. 
    1.60 +# The encoding is not always determined by the language that is chosen, 
    1.61 +# but also whether or not the output is meant for Windows or non-Windows users. 
    1.62 +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES 
    1.63 +# forces the Windows encoding (this is the default for the Windows binary), 
    1.64 +# whereas setting the tag to NO uses a Unix-style encoding (the default for 
    1.65 +# all platforms other than Windows).
    1.66 +
    1.67 +USE_WINDOWS_ENCODING   = NO
    1.68 +
    1.69 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
    1.70 +# include brief member descriptions after the members that are listed in 
    1.71 +# the file and class documentation (similar to JavaDoc). 
    1.72 +# Set to NO to disable this.
    1.73 +
    1.74 +BRIEF_MEMBER_DESC      = YES
    1.75 +
    1.76 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
    1.77 +# the brief description of a member or function before the detailed description. 
    1.78 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
    1.79 +# brief descriptions will be completely suppressed.
    1.80 +
    1.81 +REPEAT_BRIEF           = YES
    1.82 +
    1.83 +# This tag implements a quasi-intelligent brief description abbreviator 
    1.84 +# that is used to form the text in various listings. Each string 
    1.85 +# in this list, if found as the leading text of the brief description, will be 
    1.86 +# stripped from the text and the result after processing the whole list, is 
    1.87 +# used as the annotated text. Otherwise, the brief description is used as-is. 
    1.88 +# If left blank, the following values are used ("$name" is automatically 
    1.89 +# replaced with the name of the entity): "The $name class" "The $name widget" 
    1.90 +# "The $name file" "is" "provides" "specifies" "contains" 
    1.91 +# "represents" "a" "an" "the"
    1.92 +
    1.93 +ABBREVIATE_BRIEF       = 
    1.94 +
    1.95 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
    1.96 +# Doxygen will generate a detailed section even if there is only a brief 
    1.97 +# description.
    1.98 +
    1.99 +ALWAYS_DETAILED_SEC    = NO
   1.100 +
   1.101 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
   1.102 +# inherited members of a class in the documentation of that class as if those 
   1.103 +# members were ordinary class members. Constructors, destructors and assignment 
   1.104 +# operators of the base classes will not be shown.
   1.105 +
   1.106 +INLINE_INHERITED_MEMB  = NO
   1.107 +
   1.108 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
   1.109 +# path before files name in the file list and in the header files. If set 
   1.110 +# to NO the shortest path that makes the file name unique will be used.
   1.111 +
   1.112 +FULL_PATH_NAMES        = YES
   1.113 +
   1.114 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
   1.115 +# can be used to strip a user-defined part of the path. Stripping is 
   1.116 +# only done if one of the specified strings matches the left-hand part of 
   1.117 +# the path. The tag can be used to show relative paths in the file list. 
   1.118 +# If left blank the directory from which doxygen is run is used as the 
   1.119 +# path to strip.
   1.120 +
   1.121 +STRIP_FROM_PATH        = 
   1.122 +
   1.123 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
   1.124 +# the path mentioned in the documentation of a class, which tells 
   1.125 +# the reader which header file to include in order to use a class. 
   1.126 +# If left blank only the name of the header file containing the class 
   1.127 +# definition is used. Otherwise one should specify the include paths that 
   1.128 +# are normally passed to the compiler using the -I flag.
   1.129 +
   1.130 +STRIP_FROM_INC_PATH    = 
   1.131 +
   1.132 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
   1.133 +# (but less readable) file names. This can be useful is your file systems 
   1.134 +# doesn't support long names like on DOS, Mac, or CD-ROM.
   1.135 +
   1.136 +SHORT_NAMES            = NO
   1.137 +
   1.138 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
   1.139 +# will interpret the first line (until the first dot) of a JavaDoc-style 
   1.140 +# comment as the brief description. If set to NO, the JavaDoc 
   1.141 +# comments will behave just like the Qt-style comments (thus requiring an 
   1.142 +# explicit @brief command for a brief description.
   1.143 +
   1.144 +JAVADOC_AUTOBRIEF      = NO
   1.145 +
   1.146 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
   1.147 +# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
   1.148 +# comments) as a brief description. This used to be the default behaviour. 
   1.149 +# The new default is to treat a multi-line C++ comment block as a detailed 
   1.150 +# description. Set this tag to YES if you prefer the old behaviour instead.
   1.151 +
   1.152 +MULTILINE_CPP_IS_BRIEF = NO
   1.153 +
   1.154 +# If the DETAILS_AT_TOP tag is set to YES then Doxygen 
   1.155 +# will output the detailed description near the top, like JavaDoc.
   1.156 +# If set to NO, the detailed description appears after the member 
   1.157 +# documentation.
   1.158 +
   1.159 +DETAILS_AT_TOP         = NO
   1.160 +
   1.161 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
   1.162 +# member inherits the documentation from any documented member that it 
   1.163 +# re-implements.
   1.164 +
   1.165 +INHERIT_DOCS           = YES
   1.166 +
   1.167 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
   1.168 +# tag is set to YES, then doxygen will reuse the documentation of the first 
   1.169 +# member in the group (if any) for the other members of the group. By default 
   1.170 +# all members of a group must be documented explicitly.
   1.171 +
   1.172 +DISTRIBUTE_GROUP_DOC   = NO
   1.173 +
   1.174 +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
   1.175 +# a new page for each member. If set to NO, the documentation of a member will 
   1.176 +# be part of the file/class/namespace that contains it.
   1.177 +
   1.178 +SEPARATE_MEMBER_PAGES  = NO
   1.179 +
   1.180 +# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
   1.181 +# Doxygen uses this value to replace tabs by spaces in code fragments.
   1.182 +
   1.183 +TAB_SIZE               = 8
   1.184 +
   1.185 +# This tag can be used to specify a number of aliases that acts 
   1.186 +# as commands in the documentation. An alias has the form "name=value". 
   1.187 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
   1.188 +# put the command \sideeffect (or @sideeffect) in the documentation, which 
   1.189 +# will result in a user-defined paragraph with heading "Side Effects:". 
   1.190 +# You can put \n's in the value part of an alias to insert newlines.
   1.191 +
   1.192 +ALIASES                = 
   1.193 +
   1.194 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
   1.195 +# sources only. Doxygen will then generate output that is more tailored for C. 
   1.196 +# For instance, some of the names that are used will be different. The list 
   1.197 +# of all members will be omitted, etc.
   1.198 +
   1.199 +OPTIMIZE_OUTPUT_FOR_C  = YES
   1.200 +
   1.201 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
   1.202 +# only. Doxygen will then generate output that is more tailored for Java. 
   1.203 +# For instance, namespaces will be presented as packages, qualified scopes 
   1.204 +# will look different, etc.
   1.205 +
   1.206 +OPTIMIZE_OUTPUT_JAVA   = NO
   1.207 +
   1.208 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
   1.209 +# the same type (for instance a group of public functions) to be put as a 
   1.210 +# subgroup of that type (e.g. under the Public Functions section). Set it to 
   1.211 +# NO to prevent subgrouping. Alternatively, this can be done per class using 
   1.212 +# the \nosubgrouping command.
   1.213 +
   1.214 +SUBGROUPING            = YES
   1.215 +
   1.216 +#---------------------------------------------------------------------------
   1.217 +# Build related configuration options
   1.218 +#---------------------------------------------------------------------------
   1.219 +
   1.220 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
   1.221 +# documentation are documented, even if no documentation was available. 
   1.222 +# Private class members and static file members will be hidden unless 
   1.223 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
   1.224 +
   1.225 +EXTRACT_ALL            = NO
   1.226 +
   1.227 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
   1.228 +# will be included in the documentation.
   1.229 +
   1.230 +EXTRACT_PRIVATE        = NO
   1.231 +
   1.232 +# If the EXTRACT_STATIC tag is set to YES all static members of a file 
   1.233 +# will be included in the documentation.
   1.234 +
   1.235 +EXTRACT_STATIC         = NO
   1.236 +
   1.237 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
   1.238 +# defined locally in source files will be included in the documentation. 
   1.239 +# If set to NO only classes defined in header files are included.
   1.240 +
   1.241 +EXTRACT_LOCAL_CLASSES  = YES
   1.242 +
   1.243 +# This flag is only useful for Objective-C code. When set to YES local 
   1.244 +# methods, which are defined in the implementation section but not in 
   1.245 +# the interface are included in the documentation. 
   1.246 +# If set to NO (the default) only methods in the interface are included.
   1.247 +
   1.248 +EXTRACT_LOCAL_METHODS  = NO
   1.249 +
   1.250 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
   1.251 +# undocumented members of documented classes, files or namespaces. 
   1.252 +# If set to NO (the default) these members will be included in the 
   1.253 +# various overviews, but no documentation section is generated. 
   1.254 +# This option has no effect if EXTRACT_ALL is enabled.
   1.255 +
   1.256 +HIDE_UNDOC_MEMBERS     = NO
   1.257 +
   1.258 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
   1.259 +# undocumented classes that are normally visible in the class hierarchy. 
   1.260 +# If set to NO (the default) these classes will be included in the various 
   1.261 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
   1.262 +
   1.263 +HIDE_UNDOC_CLASSES     = NO
   1.264 +
   1.265 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
   1.266 +# friend (class|struct|union) declarations. 
   1.267 +# If set to NO (the default) these declarations will be included in the 
   1.268 +# documentation.
   1.269 +
   1.270 +HIDE_FRIEND_COMPOUNDS  = NO
   1.271 +
   1.272 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
   1.273 +# documentation blocks found inside the body of a function. 
   1.274 +# If set to NO (the default) these blocks will be appended to the 
   1.275 +# function's detailed documentation block.
   1.276 +
   1.277 +HIDE_IN_BODY_DOCS      = NO
   1.278 +
   1.279 +# The INTERNAL_DOCS tag determines if documentation 
   1.280 +# that is typed after a \internal command is included. If the tag is set 
   1.281 +# to NO (the default) then the documentation will be excluded. 
   1.282 +# Set it to YES to include the internal documentation.
   1.283 +
   1.284 +INTERNAL_DOCS          = NO
   1.285 +
   1.286 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
   1.287 +# file names in lower-case letters. If set to YES upper-case letters are also 
   1.288 +# allowed. This is useful if you have classes or files whose names only differ 
   1.289 +# in case and if your file system supports case sensitive file names. Windows 
   1.290 +# and Mac users are advised to set this option to NO.
   1.291 +
   1.292 +CASE_SENSE_NAMES       = YES
   1.293 +
   1.294 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
   1.295 +# will show members with their full class and namespace scopes in the 
   1.296 +# documentation. If set to YES the scope will be hidden.
   1.297 +
   1.298 +HIDE_SCOPE_NAMES       = NO
   1.299 +
   1.300 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
   1.301 +# will put a list of the files that are included by a file in the documentation 
   1.302 +# of that file.
   1.303 +
   1.304 +SHOW_INCLUDE_FILES     = YES
   1.305 +
   1.306 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
   1.307 +# is inserted in the documentation for inline members.
   1.308 +
   1.309 +INLINE_INFO            = YES
   1.310 +
   1.311 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
   1.312 +# will sort the (detailed) documentation of file and class members 
   1.313 +# alphabetically by member name. If set to NO the members will appear in 
   1.314 +# declaration order.
   1.315 +
   1.316 +SORT_MEMBER_DOCS       = YES
   1.317 +
   1.318 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
   1.319 +# brief documentation of file, namespace and class members alphabetically 
   1.320 +# by member name. If set to NO (the default) the members will appear in 
   1.321 +# declaration order.
   1.322 +
   1.323 +SORT_BRIEF_DOCS        = NO
   1.324 +
   1.325 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
   1.326 +# sorted by fully-qualified names, including namespaces. If set to 
   1.327 +# NO (the default), the class list will be sorted only by class name, 
   1.328 +# not including the namespace part. 
   1.329 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
   1.330 +# Note: This option applies only to the class list, not to the 
   1.331 +# alphabetical list.
   1.332 +
   1.333 +SORT_BY_SCOPE_NAME     = NO
   1.334 +
   1.335 +# The GENERATE_TODOLIST tag can be used to enable (YES) or 
   1.336 +# disable (NO) the todo list. This list is created by putting \todo 
   1.337 +# commands in the documentation.
   1.338 +
   1.339 +GENERATE_TODOLIST      = YES
   1.340 +
   1.341 +# The GENERATE_TESTLIST tag can be used to enable (YES) or 
   1.342 +# disable (NO) the test list. This list is created by putting \test 
   1.343 +# commands in the documentation.
   1.344 +
   1.345 +GENERATE_TESTLIST      = YES
   1.346 +
   1.347 +# The GENERATE_BUGLIST tag can be used to enable (YES) or 
   1.348 +# disable (NO) the bug list. This list is created by putting \bug 
   1.349 +# commands in the documentation.
   1.350 +
   1.351 +GENERATE_BUGLIST       = YES
   1.352 +
   1.353 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
   1.354 +# disable (NO) the deprecated list. This list is created by putting 
   1.355 +# \deprecated commands in the documentation.
   1.356 +
   1.357 +GENERATE_DEPRECATEDLIST= YES
   1.358 +
   1.359 +# The ENABLED_SECTIONS tag can be used to enable conditional 
   1.360 +# documentation sections, marked by \if sectionname ... \endif.
   1.361 +
   1.362 +ENABLED_SECTIONS       = 
   1.363 +
   1.364 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
   1.365 +# the initial value of a variable or define consists of for it to appear in 
   1.366 +# the documentation. If the initializer consists of more lines than specified 
   1.367 +# here it will be hidden. Use a value of 0 to hide initializers completely. 
   1.368 +# The appearance of the initializer of individual variables and defines in the 
   1.369 +# documentation can be controlled using \showinitializer or \hideinitializer 
   1.370 +# command in the documentation regardless of this setting.
   1.371 +
   1.372 +MAX_INITIALIZER_LINES  = 30
   1.373 +
   1.374 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
   1.375 +# at the bottom of the documentation of classes and structs. If set to YES the 
   1.376 +# list will mention the files that were used to generate the documentation.
   1.377 +
   1.378 +SHOW_USED_FILES        = YES
   1.379 +
   1.380 +# If the sources in your project are distributed over multiple directories 
   1.381 +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
   1.382 +# in the documentation. The default is YES.
   1.383 +
   1.384 +SHOW_DIRECTORIES       = YES
   1.385 +
   1.386 +# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
   1.387 +# doxygen should invoke to get the current version for each file (typically from the 
   1.388 +# version control system). Doxygen will invoke the program by executing (via 
   1.389 +# popen()) the command <command> <input-file>, where <command> is the value of 
   1.390 +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
   1.391 +# provided by doxygen. Whatever the progam writes to standard output 
   1.392 +# is used as the file version. See the manual for examples.
   1.393 +
   1.394 +FILE_VERSION_FILTER    = 
   1.395 +
   1.396 +#---------------------------------------------------------------------------
   1.397 +# configuration options related to warning and progress messages
   1.398 +#---------------------------------------------------------------------------
   1.399 +
   1.400 +# The QUIET tag can be used to turn on/off the messages that are generated 
   1.401 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
   1.402 +
   1.403 +QUIET                  = NO
   1.404 +
   1.405 +# The WARNINGS tag can be used to turn on/off the warning messages that are 
   1.406 +# generated by doxygen. Possible values are YES and NO. If left blank 
   1.407 +# NO is used.
   1.408 +
   1.409 +WARNINGS               = YES
   1.410 +
   1.411 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
   1.412 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
   1.413 +# automatically be disabled.
   1.414 +
   1.415 +WARN_IF_UNDOCUMENTED   = YES
   1.416 +
   1.417 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
   1.418 +# potential errors in the documentation, such as not documenting some 
   1.419 +# parameters in a documented function, or documenting parameters that 
   1.420 +# don't exist or using markup commands wrongly.
   1.421 +
   1.422 +WARN_IF_DOC_ERROR      = YES
   1.423 +
   1.424 +# This WARN_NO_PARAMDOC option can be abled to get warnings for 
   1.425 +# functions that are documented, but have no documentation for their parameters 
   1.426 +# or return value. If set to NO (the default) doxygen will only warn about 
   1.427 +# wrong or incomplete parameter documentation, but not about the absence of 
   1.428 +# documentation.
   1.429 +
   1.430 +WARN_NO_PARAMDOC       = NO
   1.431 +
   1.432 +# The WARN_FORMAT tag determines the format of the warning messages that 
   1.433 +# doxygen can produce. The string should contain the $file, $line, and $text 
   1.434 +# tags, which will be replaced by the file and line number from which the 
   1.435 +# warning originated and the warning text. Optionally the format may contain 
   1.436 +# $version, which will be replaced by the version of the file (if it could 
   1.437 +# be obtained via FILE_VERSION_FILTER)
   1.438 +
   1.439 +WARN_FORMAT            = "$file:$line: $text"
   1.440 +
   1.441 +# The WARN_LOGFILE tag can be used to specify a file to which warning 
   1.442 +# and error messages should be written. If left blank the output is written 
   1.443 +# to stderr.
   1.444 +
   1.445 +WARN_LOGFILE           = 
   1.446 +
   1.447 +#---------------------------------------------------------------------------
   1.448 +# configuration options related to the input files
   1.449 +#---------------------------------------------------------------------------
   1.450 +
   1.451 +# The INPUT tag can be used to specify the files and/or directories that contain 
   1.452 +# documented source files. You may enter file names like "myfile.cpp" or 
   1.453 +# directories like "/usr/src/myproject". Separate the files or directories 
   1.454 +# with spaces.
   1.455 +
   1.456 +INPUT                  = 
   1.457 +
   1.458 +# If the value of the INPUT tag contains directories, you can use the 
   1.459 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   1.460 +# and *.h) to filter out the source-files in the directories. If left 
   1.461 +# blank the following patterns are tested: 
   1.462 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
   1.463 +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
   1.464 +
   1.465 +FILE_PATTERNS          = 
   1.466 +
   1.467 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
   1.468 +# should be searched for input files as well. Possible values are YES and NO. 
   1.469 +# If left blank NO is used.
   1.470 +
   1.471 +RECURSIVE              = NO
   1.472 +
   1.473 +# The EXCLUDE tag can be used to specify files and/or directories that should 
   1.474 +# excluded from the INPUT source files. This way you can easily exclude a 
   1.475 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
   1.476 +
   1.477 +EXCLUDE                = 
   1.478 +
   1.479 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
   1.480 +# directories that are symbolic links (a Unix filesystem feature) are excluded 
   1.481 +# from the input.
   1.482 +
   1.483 +EXCLUDE_SYMLINKS       = NO
   1.484 +
   1.485 +# If the value of the INPUT tag contains directories, you can use the 
   1.486 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
   1.487 +# certain files from those directories. Note that the wildcards are matched 
   1.488 +# against the file with absolute path, so to exclude all test directories 
   1.489 +# for example use the pattern */test/*
   1.490 +
   1.491 +EXCLUDE_PATTERNS       = 
   1.492 +
   1.493 +# The EXAMPLE_PATH tag can be used to specify one or more files or 
   1.494 +# directories that contain example code fragments that are included (see 
   1.495 +# the \include command).
   1.496 +
   1.497 +EXAMPLE_PATH           = 
   1.498 +
   1.499 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   1.500 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   1.501 +# and *.h) to filter out the source-files in the directories. If left 
   1.502 +# blank all files are included.
   1.503 +
   1.504 +EXAMPLE_PATTERNS       = 
   1.505 +
   1.506 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
   1.507 +# searched for input files to be used with the \include or \dontinclude 
   1.508 +# commands irrespective of the value of the RECURSIVE tag. 
   1.509 +# Possible values are YES and NO. If left blank NO is used.
   1.510 +
   1.511 +EXAMPLE_RECURSIVE      = NO
   1.512 +
   1.513 +# The IMAGE_PATH tag can be used to specify one or more files or 
   1.514 +# directories that contain image that are included in the documentation (see 
   1.515 +# the \image command).
   1.516 +
   1.517 +IMAGE_PATH             = 
   1.518 +
   1.519 +# The INPUT_FILTER tag can be used to specify a program that doxygen should 
   1.520 +# invoke to filter for each input file. Doxygen will invoke the filter program 
   1.521 +# by executing (via popen()) the command <filter> <input-file>, where <filter> 
   1.522 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
   1.523 +# input file. Doxygen will then use the output that the filter program writes 
   1.524 +# to standard output.  If FILTER_PATTERNS is specified, this tag will be 
   1.525 +# ignored.
   1.526 +
   1.527 +INPUT_FILTER           = 
   1.528 +
   1.529 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
   1.530 +# basis.  Doxygen will compare the file name with each pattern and apply the 
   1.531 +# filter if there is a match.  The filters are a list of the form: 
   1.532 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
   1.533 +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
   1.534 +# is applied to all files.
   1.535 +
   1.536 +FILTER_PATTERNS        = 
   1.537 +
   1.538 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
   1.539 +# INPUT_FILTER) will be used to filter the input files when producing source 
   1.540 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
   1.541 +
   1.542 +FILTER_SOURCE_FILES    = NO
   1.543 +
   1.544 +#---------------------------------------------------------------------------
   1.545 +# configuration options related to source browsing
   1.546 +#---------------------------------------------------------------------------
   1.547 +
   1.548 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
   1.549 +# be generated. Documented entities will be cross-referenced with these sources. 
   1.550 +# Note: To get rid of all source code in the generated output, make sure also 
   1.551 +# VERBATIM_HEADERS is set to NO.
   1.552 +
   1.553 +SOURCE_BROWSER         = NO
   1.554 +
   1.555 +# Setting the INLINE_SOURCES tag to YES will include the body 
   1.556 +# of functions and classes directly in the documentation.
   1.557 +
   1.558 +INLINE_SOURCES         = NO
   1.559 +
   1.560 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
   1.561 +# doxygen to hide any special comment blocks from generated source code 
   1.562 +# fragments. Normal C and C++ comments will always remain visible.
   1.563 +
   1.564 +STRIP_CODE_COMMENTS    = YES
   1.565 +
   1.566 +# If the REFERENCED_BY_RELATION tag is set to YES (the default) 
   1.567 +# then for each documented function all documented 
   1.568 +# functions referencing it will be listed.
   1.569 +
   1.570 +REFERENCED_BY_RELATION = YES
   1.571 +
   1.572 +# If the REFERENCES_RELATION tag is set to YES (the default) 
   1.573 +# then for each documented function all documented entities 
   1.574 +# called/used by that function will be listed.
   1.575 +
   1.576 +REFERENCES_RELATION    = YES
   1.577 +
   1.578 +# If the USE_HTAGS tag is set to YES then the references to source code 
   1.579 +# will point to the HTML generated by the htags(1) tool instead of doxygen 
   1.580 +# built-in source browser. The htags tool is part of GNU's global source 
   1.581 +# tagging system (see http://www.gnu.org/software/global/global.html). You 
   1.582 +# will need version 4.8.6 or higher.
   1.583 +
   1.584 +USE_HTAGS              = NO
   1.585 +
   1.586 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
   1.587 +# will generate a verbatim copy of the header file for each class for 
   1.588 +# which an include is specified. Set to NO to disable this.
   1.589 +
   1.590 +VERBATIM_HEADERS       = YES
   1.591 +
   1.592 +#---------------------------------------------------------------------------
   1.593 +# configuration options related to the alphabetical class index
   1.594 +#---------------------------------------------------------------------------
   1.595 +
   1.596 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
   1.597 +# of all compounds will be generated. Enable this if the project 
   1.598 +# contains a lot of classes, structs, unions or interfaces.
   1.599 +
   1.600 +ALPHABETICAL_INDEX     = NO
   1.601 +
   1.602 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
   1.603 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
   1.604 +# in which this list will be split (can be a number in the range [1..20])
   1.605 +
   1.606 +COLS_IN_ALPHA_INDEX    = 5
   1.607 +
   1.608 +# In case all classes in a project start with a common prefix, all 
   1.609 +# classes will be put under the same header in the alphabetical index. 
   1.610 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
   1.611 +# should be ignored while generating the index headers.
   1.612 +
   1.613 +IGNORE_PREFIX          = 
   1.614 +
   1.615 +#---------------------------------------------------------------------------
   1.616 +# configuration options related to the HTML output
   1.617 +#---------------------------------------------------------------------------
   1.618 +
   1.619 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
   1.620 +# generate HTML output.
   1.621 +
   1.622 +GENERATE_HTML          = YES
   1.623 +
   1.624 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
   1.625 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.626 +# put in front of it. If left blank `html' will be used as the default path.
   1.627 +
   1.628 +HTML_OUTPUT            = html
   1.629 +
   1.630 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
   1.631 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
   1.632 +# doxygen will generate files with .html extension.
   1.633 +
   1.634 +HTML_FILE_EXTENSION    = .html
   1.635 +
   1.636 +# The HTML_HEADER tag can be used to specify a personal HTML header for 
   1.637 +# each generated HTML page. If it is left blank doxygen will generate a 
   1.638 +# standard header.
   1.639 +
   1.640 +HTML_HEADER            = 
   1.641 +
   1.642 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
   1.643 +# each generated HTML page. If it is left blank doxygen will generate a 
   1.644 +# standard footer.
   1.645 +
   1.646 +HTML_FOOTER            = 
   1.647 +
   1.648 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
   1.649 +# style sheet that is used by each HTML page. It can be used to 
   1.650 +# fine-tune the look of the HTML output. If the tag is left blank doxygen 
   1.651 +# will generate a default style sheet. Note that doxygen will try to copy 
   1.652 +# the style sheet file to the HTML output directory, so don't put your own 
   1.653 +# stylesheet in the HTML output directory as well, or it will be erased!
   1.654 +
   1.655 +HTML_STYLESHEET        = 
   1.656 +
   1.657 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
   1.658 +# files or namespaces will be aligned in HTML using tables. If set to 
   1.659 +# NO a bullet list will be used.
   1.660 +
   1.661 +HTML_ALIGN_MEMBERS     = YES
   1.662 +
   1.663 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
   1.664 +# will be generated that can be used as input for tools like the 
   1.665 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
   1.666 +# of the generated HTML documentation.
   1.667 +
   1.668 +GENERATE_HTMLHELP      = NO
   1.669 +
   1.670 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
   1.671 +# be used to specify the file name of the resulting .chm file. You 
   1.672 +# can add a path in front of the file if the result should not be 
   1.673 +# written to the html output directory.
   1.674 +
   1.675 +CHM_FILE               = 
   1.676 +
   1.677 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
   1.678 +# be used to specify the location (absolute path including file name) of 
   1.679 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
   1.680 +# the HTML help compiler on the generated index.hhp.
   1.681 +
   1.682 +HHC_LOCATION           = 
   1.683 +
   1.684 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
   1.685 +# controls if a separate .chi index file is generated (YES) or that 
   1.686 +# it should be included in the master .chm file (NO).
   1.687 +
   1.688 +GENERATE_CHI           = NO
   1.689 +
   1.690 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
   1.691 +# controls whether a binary table of contents is generated (YES) or a 
   1.692 +# normal table of contents (NO) in the .chm file.
   1.693 +
   1.694 +BINARY_TOC             = NO
   1.695 +
   1.696 +# The TOC_EXPAND flag can be set to YES to add extra items for group members 
   1.697 +# to the contents of the HTML help documentation and to the tree view.
   1.698 +
   1.699 +TOC_EXPAND             = NO
   1.700 +
   1.701 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
   1.702 +# top of each HTML page. The value NO (the default) enables the index and 
   1.703 +# the value YES disables it.
   1.704 +
   1.705 +DISABLE_INDEX          = NO
   1.706 +
   1.707 +# This tag can be used to set the number of enum values (range [1..20]) 
   1.708 +# that doxygen will group on one line in the generated HTML documentation.
   1.709 +
   1.710 +ENUM_VALUES_PER_LINE   = 4
   1.711 +
   1.712 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
   1.713 +# generated containing a tree-like index structure (just like the one that 
   1.714 +# is generated for HTML Help). For this to work a browser that supports 
   1.715 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 
   1.716 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 
   1.717 +# probably better off using the HTML help feature.
   1.718 +
   1.719 +GENERATE_TREEVIEW      = NO
   1.720 +
   1.721 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
   1.722 +# used to set the initial width (in pixels) of the frame in which the tree 
   1.723 +# is shown.
   1.724 +
   1.725 +TREEVIEW_WIDTH         = 250
   1.726 +
   1.727 +#---------------------------------------------------------------------------
   1.728 +# configuration options related to the LaTeX output
   1.729 +#---------------------------------------------------------------------------
   1.730 +
   1.731 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
   1.732 +# generate Latex output.
   1.733 +
   1.734 +GENERATE_LATEX         = YES
   1.735 +
   1.736 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
   1.737 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.738 +# put in front of it. If left blank `latex' will be used as the default path.
   1.739 +
   1.740 +LATEX_OUTPUT           = latex
   1.741 +
   1.742 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
   1.743 +# invoked. If left blank `latex' will be used as the default command name.
   1.744 +
   1.745 +LATEX_CMD_NAME         = latex
   1.746 +
   1.747 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
   1.748 +# generate index for LaTeX. If left blank `makeindex' will be used as the 
   1.749 +# default command name.
   1.750 +
   1.751 +MAKEINDEX_CMD_NAME     = makeindex
   1.752 +
   1.753 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
   1.754 +# LaTeX documents. This may be useful for small projects and may help to 
   1.755 +# save some trees in general.
   1.756 +
   1.757 +COMPACT_LATEX          = NO
   1.758 +
   1.759 +# The PAPER_TYPE tag can be used to set the paper type that is used 
   1.760 +# by the printer. Possible values are: a4, a4wide, letter, legal and 
   1.761 +# executive. If left blank a4wide will be used.
   1.762 +
   1.763 +PAPER_TYPE             = a4wide
   1.764 +
   1.765 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
   1.766 +# packages that should be included in the LaTeX output.
   1.767 +
   1.768 +EXTRA_PACKAGES         = 
   1.769 +
   1.770 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
   1.771 +# the generated latex document. The header should contain everything until 
   1.772 +# the first chapter. If it is left blank doxygen will generate a 
   1.773 +# standard header. Notice: only use this tag if you know what you are doing!
   1.774 +
   1.775 +LATEX_HEADER           = 
   1.776 +
   1.777 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
   1.778 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
   1.779 +# contain links (just like the HTML output) instead of page references 
   1.780 +# This makes the output suitable for online browsing using a pdf viewer.
   1.781 +
   1.782 +PDF_HYPERLINKS         = NO
   1.783 +
   1.784 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
   1.785 +# plain latex in the generated Makefile. Set this option to YES to get a 
   1.786 +# higher quality PDF documentation.
   1.787 +
   1.788 +USE_PDFLATEX           = NO
   1.789 +
   1.790 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
   1.791 +# command to the generated LaTeX files. This will instruct LaTeX to keep 
   1.792 +# running if errors occur, instead of asking the user for help. 
   1.793 +# This option is also used when generating formulas in HTML.
   1.794 +
   1.795 +LATEX_BATCHMODE        = NO
   1.796 +
   1.797 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
   1.798 +# include the index chapters (such as File Index, Compound Index, etc.) 
   1.799 +# in the output.
   1.800 +
   1.801 +LATEX_HIDE_INDICES     = NO
   1.802 +
   1.803 +#---------------------------------------------------------------------------
   1.804 +# configuration options related to the RTF output
   1.805 +#---------------------------------------------------------------------------
   1.806 +
   1.807 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
   1.808 +# The RTF output is optimized for Word 97 and may not look very pretty with 
   1.809 +# other RTF readers or editors.
   1.810 +
   1.811 +GENERATE_RTF           = NO
   1.812 +
   1.813 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
   1.814 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.815 +# put in front of it. If left blank `rtf' will be used as the default path.
   1.816 +
   1.817 +RTF_OUTPUT             = rtf
   1.818 +
   1.819 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
   1.820 +# RTF documents. This may be useful for small projects and may help to 
   1.821 +# save some trees in general.
   1.822 +
   1.823 +COMPACT_RTF            = NO
   1.824 +
   1.825 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
   1.826 +# will contain hyperlink fields. The RTF file will 
   1.827 +# contain links (just like the HTML output) instead of page references. 
   1.828 +# This makes the output suitable for online browsing using WORD or other 
   1.829 +# programs which support those fields. 
   1.830 +# Note: wordpad (write) and others do not support links.
   1.831 +
   1.832 +RTF_HYPERLINKS         = NO
   1.833 +
   1.834 +# Load stylesheet definitions from file. Syntax is similar to doxygen's 
   1.835 +# config file, i.e. a series of assignments. You only have to provide 
   1.836 +# replacements, missing definitions are set to their default value.
   1.837 +
   1.838 +RTF_STYLESHEET_FILE    = 
   1.839 +
   1.840 +# Set optional variables used in the generation of an rtf document. 
   1.841 +# Syntax is similar to doxygen's config file.
   1.842 +
   1.843 +RTF_EXTENSIONS_FILE    = 
   1.844 +
   1.845 +#---------------------------------------------------------------------------
   1.846 +# configuration options related to the man page output
   1.847 +#---------------------------------------------------------------------------
   1.848 +
   1.849 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
   1.850 +# generate man pages
   1.851 +
   1.852 +GENERATE_MAN           = YES
   1.853 +
   1.854 +# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
   1.855 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.856 +# put in front of it. If left blank `man' will be used as the default path.
   1.857 +
   1.858 +MAN_OUTPUT             = man
   1.859 +
   1.860 +# The MAN_EXTENSION tag determines the extension that is added to 
   1.861 +# the generated man pages (default is the subroutine's section .3)
   1.862 +
   1.863 +MAN_EXTENSION          = .3
   1.864 +
   1.865 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
   1.866 +# then it will generate one additional man file for each entity 
   1.867 +# documented in the real man page(s). These additional files 
   1.868 +# only source the real man page, but without them the man command 
   1.869 +# would be unable to find the correct page. The default is NO.
   1.870 +
   1.871 +MAN_LINKS              = NO
   1.872 +
   1.873 +#---------------------------------------------------------------------------
   1.874 +# configuration options related to the XML output
   1.875 +#---------------------------------------------------------------------------
   1.876 +
   1.877 +# If the GENERATE_XML tag is set to YES Doxygen will 
   1.878 +# generate an XML file that captures the structure of 
   1.879 +# the code including all documentation.
   1.880 +
   1.881 +GENERATE_XML           = NO
   1.882 +
   1.883 +# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
   1.884 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.885 +# put in front of it. If left blank `xml' will be used as the default path.
   1.886 +
   1.887 +XML_OUTPUT             = xml
   1.888 +
   1.889 +# The XML_SCHEMA tag can be used to specify an XML schema, 
   1.890 +# which can be used by a validating XML parser to check the 
   1.891 +# syntax of the XML files.
   1.892 +
   1.893 +XML_SCHEMA             = 
   1.894 +
   1.895 +# The XML_DTD tag can be used to specify an XML DTD, 
   1.896 +# which can be used by a validating XML parser to check the 
   1.897 +# syntax of the XML files.
   1.898 +
   1.899 +XML_DTD                = 
   1.900 +
   1.901 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
   1.902 +# dump the program listings (including syntax highlighting 
   1.903 +# and cross-referencing information) to the XML output. Note that 
   1.904 +# enabling this will significantly increase the size of the XML output.
   1.905 +
   1.906 +XML_PROGRAMLISTING     = YES
   1.907 +
   1.908 +#---------------------------------------------------------------------------
   1.909 +# configuration options for the AutoGen Definitions output
   1.910 +#---------------------------------------------------------------------------
   1.911 +
   1.912 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
   1.913 +# generate an AutoGen Definitions (see autogen.sf.net) file 
   1.914 +# that captures the structure of the code including all 
   1.915 +# documentation. Note that this feature is still experimental 
   1.916 +# and incomplete at the moment.
   1.917 +
   1.918 +GENERATE_AUTOGEN_DEF   = NO
   1.919 +
   1.920 +#---------------------------------------------------------------------------
   1.921 +# configuration options related to the Perl module output
   1.922 +#---------------------------------------------------------------------------
   1.923 +
   1.924 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
   1.925 +# generate a Perl module file that captures the structure of 
   1.926 +# the code including all documentation. Note that this 
   1.927 +# feature is still experimental and incomplete at the 
   1.928 +# moment.
   1.929 +
   1.930 +GENERATE_PERLMOD       = NO
   1.931 +
   1.932 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
   1.933 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
   1.934 +# to generate PDF and DVI output from the Perl module output.
   1.935 +
   1.936 +PERLMOD_LATEX          = NO
   1.937 +
   1.938 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
   1.939 +# nicely formatted so it can be parsed by a human reader.  This is useful 
   1.940 +# if you want to understand what is going on.  On the other hand, if this 
   1.941 +# tag is set to NO the size of the Perl module output will be much smaller 
   1.942 +# and Perl will parse it just the same.
   1.943 +
   1.944 +PERLMOD_PRETTY         = YES
   1.945 +
   1.946 +# The names of the make variables in the generated doxyrules.make file 
   1.947 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
   1.948 +# This is useful so different doxyrules.make files included by the same 
   1.949 +# Makefile don't overwrite each other's variables.
   1.950 +
   1.951 +PERLMOD_MAKEVAR_PREFIX = 
   1.952 +
   1.953 +#---------------------------------------------------------------------------
   1.954 +# Configuration options related to the preprocessor   
   1.955 +#---------------------------------------------------------------------------
   1.956 +
   1.957 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
   1.958 +# evaluate all C-preprocessor directives found in the sources and include 
   1.959 +# files.
   1.960 +
   1.961 +ENABLE_PREPROCESSING   = YES
   1.962 +
   1.963 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
   1.964 +# names in the source code. If set to NO (the default) only conditional 
   1.965 +# compilation will be performed. Macro expansion can be done in a controlled 
   1.966 +# way by setting EXPAND_ONLY_PREDEF to YES.
   1.967 +
   1.968 +MACRO_EXPANSION        = YES
   1.969 +
   1.970 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
   1.971 +# then the macro expansion is limited to the macros specified with the 
   1.972 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
   1.973 +
   1.974 +EXPAND_ONLY_PREDEF     = YES
   1.975 +
   1.976 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
   1.977 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
   1.978 +
   1.979 +SEARCH_INCLUDES        = YES
   1.980 +
   1.981 +# The INCLUDE_PATH tag can be used to specify one or more directories that 
   1.982 +# contain include files that are not input files but should be processed by 
   1.983 +# the preprocessor.
   1.984 +
   1.985 +INCLUDE_PATH           = 
   1.986 +
   1.987 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
   1.988 +# patterns (like *.h and *.hpp) to filter out the header-files in the 
   1.989 +# directories. If left blank, the patterns specified with FILE_PATTERNS will 
   1.990 +# be used.
   1.991 +
   1.992 +INCLUDE_FILE_PATTERNS  = 
   1.993 +
   1.994 +# The PREDEFINED tag can be used to specify one or more macro names that 
   1.995 +# are defined before the preprocessor is started (similar to the -D option of 
   1.996 +# gcc). The argument of the tag is a list of macros of the form: name 
   1.997 +# or name=definition (no spaces). If the definition and the = are 
   1.998 +# omitted =1 is assumed. To prevent a macro definition from being 
   1.999 +# undefined via #undef or recursively expanded use the := operator 
  1.1000 +# instead of the = operator.
  1.1001 +
  1.1002 +PREDEFINED             = DOXYGEN_SHOULD_IGNORE_THIS=1 \
  1.1003 +                         DECLSPEC= SDLCALL=
  1.1004 +
  1.1005 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
  1.1006 +# this tag can be used to specify a list of macro names that should be expanded. 
  1.1007 +# The macro definition that is found in the sources will be used. 
  1.1008 +# Use the PREDEFINED tag if you want to use a different macro definition.
  1.1009 +
  1.1010 +EXPAND_AS_DEFINED      = 
  1.1011 +
  1.1012 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
  1.1013 +# doxygen's preprocessor will remove all function-like macros that are alone 
  1.1014 +# on a line, have an all uppercase name, and do not end with a semicolon. Such 
  1.1015 +# function macros are typically used for boiler-plate code, and will confuse 
  1.1016 +# the parser if not removed.
  1.1017 +
  1.1018 +SKIP_FUNCTION_MACROS   = YES
  1.1019 +
  1.1020 +#---------------------------------------------------------------------------
  1.1021 +# Configuration::additions related to external references   
  1.1022 +#---------------------------------------------------------------------------
  1.1023 +
  1.1024 +# The TAGFILES option can be used to specify one or more tagfiles. 
  1.1025 +# Optionally an initial location of the external documentation 
  1.1026 +# can be added for each tagfile. The format of a tag file without 
  1.1027 +# this location is as follows: 
  1.1028 +#   TAGFILES = file1 file2 ... 
  1.1029 +# Adding location for the tag files is done as follows: 
  1.1030 +#   TAGFILES = file1=loc1 "file2 = loc2" ... 
  1.1031 +# where "loc1" and "loc2" can be relative or absolute paths or 
  1.1032 +# URLs. If a location is present for each tag, the installdox tool 
  1.1033 +# does not have to be run to correct the links.
  1.1034 +# Note that each tag file must have a unique name
  1.1035 +# (where the name does NOT include the path)
  1.1036 +# If a tag file is not located in the directory in which doxygen 
  1.1037 +# is run, you must also specify the path to the tagfile here.
  1.1038 +
  1.1039 +TAGFILES               = 
  1.1040 +
  1.1041 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
  1.1042 +# a tag file that is based on the input files it reads.
  1.1043 +
  1.1044 +GENERATE_TAGFILE       = 
  1.1045 +
  1.1046 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
  1.1047 +# in the class index. If set to NO only the inherited external classes 
  1.1048 +# will be listed.
  1.1049 +
  1.1050 +ALLEXTERNALS           = NO
  1.1051 +
  1.1052 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
  1.1053 +# in the modules index. If set to NO, only the current project's groups will 
  1.1054 +# be listed.
  1.1055 +
  1.1056 +EXTERNAL_GROUPS        = YES
  1.1057 +
  1.1058 +# The PERL_PATH should be the absolute path and name of the perl script 
  1.1059 +# interpreter (i.e. the result of `which perl').
  1.1060 +
  1.1061 +PERL_PATH              = /usr/bin/perl
  1.1062 +
  1.1063 +#---------------------------------------------------------------------------
  1.1064 +# Configuration options related to the dot tool   
  1.1065 +#---------------------------------------------------------------------------
  1.1066 +
  1.1067 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
  1.1068 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
  1.1069 +# or super classes. Setting the tag to NO turns the diagrams off. Note that 
  1.1070 +# this option is superseded by the HAVE_DOT option below. This is only a 
  1.1071 +# fallback. It is recommended to install and use dot, since it yields more 
  1.1072 +# powerful graphs.
  1.1073 +
  1.1074 +CLASS_DIAGRAMS         = NO
  1.1075 +
  1.1076 +# If set to YES, the inheritance and collaboration graphs will hide 
  1.1077 +# inheritance and usage relations if the target is undocumented 
  1.1078 +# or is not a class.
  1.1079 +
  1.1080 +HIDE_UNDOC_RELATIONS   = YES
  1.1081 +
  1.1082 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
  1.1083 +# available from the path. This tool is part of Graphviz, a graph visualization 
  1.1084 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
  1.1085 +# have no effect if this option is set to NO (the default)
  1.1086 +
  1.1087 +HAVE_DOT               = NO
  1.1088 +
  1.1089 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1.1090 +# will generate a graph for each documented class showing the direct and 
  1.1091 +# indirect inheritance relations. Setting this tag to YES will force the 
  1.1092 +# the CLASS_DIAGRAMS tag to NO.
  1.1093 +
  1.1094 +CLASS_GRAPH            = YES
  1.1095 +
  1.1096 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1.1097 +# will generate a graph for each documented class showing the direct and 
  1.1098 +# indirect implementation dependencies (inheritance, containment, and 
  1.1099 +# class references variables) of the class with other documented classes.
  1.1100 +
  1.1101 +COLLABORATION_GRAPH    = YES
  1.1102 +
  1.1103 +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
  1.1104 +# will generate a graph for groups, showing the direct groups dependencies
  1.1105 +
  1.1106 +GROUP_GRAPHS           = YES
  1.1107 +
  1.1108 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
  1.1109 +# collaboration diagrams in a style similar to the OMG's Unified Modeling 
  1.1110 +# Language.
  1.1111 +
  1.1112 +UML_LOOK               = NO
  1.1113 +
  1.1114 +# If set to YES, the inheritance and collaboration graphs will show the 
  1.1115 +# relations between templates and their instances.
  1.1116 +
  1.1117 +TEMPLATE_RELATIONS     = NO
  1.1118 +
  1.1119 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
  1.1120 +# tags are set to YES then doxygen will generate a graph for each documented 
  1.1121 +# file showing the direct and indirect include dependencies of the file with 
  1.1122 +# other documented files.
  1.1123 +
  1.1124 +INCLUDE_GRAPH          = NO
  1.1125 +
  1.1126 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
  1.1127 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
  1.1128 +# documented header file showing the documented files that directly or 
  1.1129 +# indirectly include this file.
  1.1130 +
  1.1131 +INCLUDED_BY_GRAPH      = YES
  1.1132 +
  1.1133 +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will 
  1.1134 +# generate a call dependency graph for every global function or class method. 
  1.1135 +# Note that enabling this option will significantly increase the time of a run. 
  1.1136 +# So in most cases it will be better to enable call graphs for selected 
  1.1137 +# functions only using the \callgraph command.
  1.1138 +
  1.1139 +CALL_GRAPH             = NO
  1.1140 +
  1.1141 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
  1.1142 +# will graphical hierarchy of all classes instead of a textual one.
  1.1143 +
  1.1144 +GRAPHICAL_HIERARCHY    = YES
  1.1145 +
  1.1146 +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
  1.1147 +# then doxygen will show the dependencies a directory has on other directories 
  1.1148 +# in a graphical way. The dependency relations are determined by the #include
  1.1149 +# relations between the files in the directories.
  1.1150 +
  1.1151 +DIRECTORY_GRAPH        = YES
  1.1152 +
  1.1153 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
  1.1154 +# generated by dot. Possible values are png, jpg, or gif
  1.1155 +# If left blank png will be used.
  1.1156 +
  1.1157 +DOT_IMAGE_FORMAT       = png
  1.1158 +
  1.1159 +# The tag DOT_PATH can be used to specify the path where the dot tool can be 
  1.1160 +# found. If left blank, it is assumed the dot tool can be found in the path.
  1.1161 +
  1.1162 +DOT_PATH               = 
  1.1163 +
  1.1164 +# The DOTFILE_DIRS tag can be used to specify one or more directories that 
  1.1165 +# contain dot files that are included in the documentation (see the 
  1.1166 +# \dotfile command).
  1.1167 +
  1.1168 +DOTFILE_DIRS           = 
  1.1169 +
  1.1170 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 
  1.1171 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
  1.1172 +# this value, doxygen will try to truncate the graph, so that it fits within 
  1.1173 +# the specified constraint. Beware that most browsers cannot cope with very 
  1.1174 +# large images.
  1.1175 +
  1.1176 +MAX_DOT_GRAPH_WIDTH    = 1024
  1.1177 +
  1.1178 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 
  1.1179 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
  1.1180 +# this value, doxygen will try to truncate the graph, so that it fits within 
  1.1181 +# the specified constraint. Beware that most browsers cannot cope with very 
  1.1182 +# large images.
  1.1183 +
  1.1184 +MAX_DOT_GRAPH_HEIGHT   = 1024
  1.1185 +
  1.1186 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
  1.1187 +# graphs generated by dot. A depth value of 3 means that only nodes reachable 
  1.1188 +# from the root by following a path via at most 3 edges will be shown. Nodes 
  1.1189 +# that lay further from the root node will be omitted. Note that setting this 
  1.1190 +# option to 1 or 2 may greatly reduce the computation time needed for large 
  1.1191 +# code bases. Also note that a graph may be further truncated if the graph's 
  1.1192 +# image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH 
  1.1193 +# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), 
  1.1194 +# the graph is not depth-constrained.
  1.1195 +
  1.1196 +MAX_DOT_GRAPH_DEPTH    = 0
  1.1197 +
  1.1198 +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
  1.1199 +# background. This is disabled by default, which results in a white background. 
  1.1200 +# Warning: Depending on the platform used, enabling this option may lead to 
  1.1201 +# badly anti-aliased labels on the edges of a graph (i.e. they become hard to 
  1.1202 +# read).
  1.1203 +
  1.1204 +DOT_TRANSPARENT        = NO
  1.1205 +
  1.1206 +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
  1.1207 +# files in one run (i.e. multiple -o and -T options on the command line). This 
  1.1208 +# makes dot run faster, but since only newer versions of dot (>1.8.10) 
  1.1209 +# support this, this feature is disabled by default.
  1.1210 +
  1.1211 +DOT_MULTI_TARGETS      = NO
  1.1212 +
  1.1213 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
  1.1214 +# generate a legend page explaining the meaning of the various boxes and 
  1.1215 +# arrows in the dot generated graphs.
  1.1216 +
  1.1217 +GENERATE_LEGEND        = YES
  1.1218 +
  1.1219 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
  1.1220 +# remove the intermediate dot files that are used to generate 
  1.1221 +# the various graphs.
  1.1222 +
  1.1223 +DOT_CLEANUP            = YES
  1.1224 +
  1.1225 +#---------------------------------------------------------------------------
  1.1226 +# Configuration::additions related to the search engine   
  1.1227 +#---------------------------------------------------------------------------
  1.1228 +
  1.1229 +# The SEARCHENGINE tag specifies whether or not a search engine should be 
  1.1230 +# used. If set to NO the values of all tags below this one will be ignored.
  1.1231 +
  1.1232 +SEARCHENGINE           = NO