Lines Matching refs:in

6 # All text after a double hash (##) is considered a comment and is placed in
20 # This tag specifies the encoding used for all characters in the config file
31 # project for which the documentation is generated. This name is used in the
32 # title of most generated pages and in a few other places.
49 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
97 # descriptions after the members that are listed in the file and class
113 # used to form the text in various listings. Each string in this list, if found
131 # inherited members of a class in the documentation of that class as if those
139 # before files name in the file list and in the header files. If set to NO the
147 # part of the path. The tag can be used to show relative paths in the file list.
158 # path mentioned in the documentation of a class, which tells the reader which
159 # header file to include in order to use a class. If left blank only the name of
215 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
216 # uses this value to replace tabs by spaces in code fragments.
221 # This tag can be used to specify a number of aliases that act as commands in
226 # will allow you to put the command \sideeffect (or @sideeffect) in the
227 # documentation, which will result in a user-defined paragraph with heading
228 # "Side Effects:". You can put \n's in the value part of an alias to insert
235 # will allow you to use the command class in the itcl::class meaning.
269 # extension. Doxygen has a built-in mapping, but you can override or extend it
290 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
298 # be prevented in individual cases by by putting a % sign in front of the word
306 # tag to YES in order to let doxygen match functions declarations and
330 # doxygen to replace the get and set methods by a property in the documentation.
338 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
340 # member in the group (if any) for the other members of the group. By default
356 # are shown inside the group in which they are included (e.g. using \ingroup)
360 # Note that this feature does not work in combination with
367 # with only public data fields or simple typedef fields will be shown inline in
368 # the documentation of the scope in which they are defined (i.e. file,
378 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
381 # useful for C code in case the coding convention dictates that all compound
389 # an expensive process and often the same symbol appears multiple times in the
404 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
415 # be included in the documentation.
421 # scope will be included in the documentation.
427 # included in the documentation.
433 # locally in source files will be included in the documentation. If set to NO
434 # only classes defined in header files are included. Does not have any effect
441 # which are defined in the implementation section but not in the interface are
442 # included in the documentation. If set to NO only methods in the interface are
449 # extracted and appear in the documentation as a namespace called
459 # members will be included in the various overviews, but no documentation
466 # undocumented classes that are normally visible in the class hierarchy. If set
467 # to NO these classes will be included in the various overviews. This option has
475 # included in the documentation.
495 # names in lower-case letters. If set to YES upper-case letters are also
497 # in case and if your file system supports case sensitive file names. Windows
504 # their full class and namespace scopes in the documentation. If set to YES the
511 # the files that are included by a file in the documentation of that file.
518 # which file to include in order to use the member.
524 # files with double quotes in the documentation rather than with sharp brackets.
529 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
537 # name. If set to NO the members will appear in declaration order.
544 # name. If set to NO the members will appear in declaration order. Note that
545 # this will also influence the order of the classes in the class list.
552 # destructors are listed first. If set to NO the constructors will appear in the
564 # appear in their defined order.
584 # accept a match between prototype and implementation in such cases.
590 # todo list. This list is created by putting \todo commands in the
597 # test list. This list is created by putting \test commands in the
604 # list. This list is created by putting \bug commands in the documentation.
610 # the deprecated list. This list is created by putting \deprecated commands in
623 # initial value of a variable or macro / define can have for it to appear in the
627 # controlled using \showinitializer or \hideinitializer command in the
666 # output files in an output format independent way. To create the layout file
682 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
715 # potential errors in the documentation, such as not documenting some parameters
716 # in a documented function, or documenting parameters that don't exist or using
770 # *.h) to filter out the source-files in the directories. If left blank the
830 # *.h) to filter out the source-files in the directories. If left blank all
843 # that contain images that are to be included in the documentation (see the
903 # Note: To get rid of all source code in the generated output, make sure that
935 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
942 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
953 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
960 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
964 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
965 # tools must be available from the command line (i.e. in the search path).
985 # rich C++ code for which doxygen's built-in parser lacks the necessary type
1012 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1019 # In case all classes in a project start with a common prefix, all classes will
1020 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1037 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1087 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1100 # stylesheet in the list overrules the setting of the previous ones in the
1109 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1117 # will adjust the colors in the stylesheet and background images according to
1128 # in the HTML output. For a value of 0 the output will use grayscales only. A
1136 # luminance component of the colors in the HTML output. Values below 100
1163 # shown in the various tree structured indices initially; the user can expand
1168 # representing an infinite number of entries and will result in a full expanded
1179 # Makefile in the HTML output directory. Running make will produce the docset in
1180 # that directory and running make install will install the docset in
1228 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1230 # words in the documentation. The HTML workshop also contains a viewer for
1238 # file. You can add a path in front of the file if the result should not be
1253 # YES) or that it should be included in the master .chm file ( NO).
1266 # YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
1345 # install this plugin and make it available under the help contents menu in
1367 # it. Since the tabs in the index contain the same information as the navigation
1392 # doxygen will group on one line in the generated HTML documentation.
1395 # in the overview section.
1402 # to set the initial width (in pixels) of the frame in which the tree is shown.
1409 # external symbols imported via tag files in a separate window.
1415 # Use this tag to change the font size of LaTeX formulas included as images in
1428 # Note that when changing this option you need to delete any form_*.png files in
1438 # installed or if you want to formulas look prettier in the HTML output. When
1554 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1580 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1591 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1607 # trees in general.
1623 # that should be included in the LaTeX output. To get the times font for
1686 # when generating formulas in HTML.
1693 # index chapters (such as File Index, Compound Index, etc.) in the output.
1700 # code with syntax highlighting in the LaTeX output.
1729 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1738 # trees in general.
1766 # Set optional variables used in the generation of an RTF document. Syntax is
1784 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1802 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1809 # will generate one additional man file for each entity documented in the real
1828 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1855 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1913 # The names of the make variables in the generated doxyrules.make file are
1914 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
1926 # C-preprocessor directives found in the sources and include files.
1932 # in the source code. If set to NO only conditional compilation will be
1933 # performed. Macro expansion can be done in a controlled way by setting
1948 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
1963 # patterns (like *.h and *.hpp) to filter out the header-files in the
1982 # macro definition that is found in the sources will be used. Use the PREDEFINED
1984 # definition found in the source code.
2013 # the path). If a tag file is not located in the directory in which doxygen is
2024 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
2030 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2037 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2055 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2065 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2067 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2072 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2073 # then run dia to produce the diagram and insert it in the documentation. The
2075 # If left empty dia is assumed to be found in the default search path.
2088 # Bell Labs. The other options in this section have no effect if this option is
2095 # to run in parallel. When set to 0 doxygen will base this on the number of
2096 # processors available in the system. You can set it explicitly to a value
2104 # When you want a differently looking font in the dot files that doxygen
2106 # sure dot is able to find the font, which can be done by putting it in a
2114 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2153 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2203 # So in most cases it will be better to enable call graphs for selected
2214 # So in most cases it will be better to enable caller graphs for selected
2229 # dependencies a directory has on other directories in a graphical way. The
2231 # files in the directories.
2239 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2240 # to make the SVG files visible in IE 9+ (other browsers do not have this
2255 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2263 # found. If left blank, it is assumed the dot tool can be found in the path.
2269 # contain dot files that are included in the documentation (see the \dotfile
2276 # contain msc files that are included in the documentation (see the \mscfile
2282 # contain dia files that are included in the documentation (see the \diafile
2290 # generate a warning when it encounters a \startuml command in this case and
2297 # that will be shown in the graph. If the number of nodes in a graph becomes
2300 # children of the root node in a graph is already larger than
2333 # files in one run (i.e. multiple -o and -T options on the command line). This
2342 # explaining the meaning of the various boxes and arrows in the dot generated