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
73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
75 # information to generate all constant output in the proper language.
89 # descriptions after the members that are listed in the file and class
105 # used to form the text in various listings. Each string in this list, if found
123 # inherited members of a class in the documentation of that class as if those
131 # before files name in the file list and in the header files. If set to NO the
139 # part of the path. The tag can be used to show relative paths in the file list.
150 # path mentioned in the documentation of a class, which tells the reader which
151 # header file to include in order to use a class. If left blank only the name of
207 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
208 # uses this value to replace tabs by spaces in code fragments.
213 # This tag can be used to specify a number of aliases that act as commands in
218 # will allow you to put the command \sideeffect (or @sideeffect) in the
219 # documentation, which will result in a user-defined paragraph with heading
220 # "Side Effects:". You can put \n's in the value part of an alias to insert
227 # will allow you to use the command class in the itcl::class meaning.
261 # extension. Doxygen has a built-in mapping, but you can override or extend it
279 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
287 # be prevented in individual cases by by putting a % sign in front of the word
295 # tag to YES in order to let doxygen match functions declarations and
319 # doxygen to replace the get and set methods by a property in the documentation.
327 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
329 # member in the group (if any) for the other members of the group. By default
345 # are shown inside the group in which they are included (e.g. using \ingroup)
349 # Note that this feature does not work in combination with
356 # with only public data fields or simple typedef fields will be shown inline in
357 # the documentation of the scope in which they are defined (i.e. file,
367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
370 # useful for C code in case the coding convention dictates that all compound
378 # an expensive process and often the same symbol appears multiple times in the
393 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
404 # be included in the documentation.
410 # scope will be included in the documentation.
416 # included in the documentation.
422 # locally in source files will be included in the documentation. If set to NO
423 # only classes defined in header files are included. Does not have any effect
430 # which are defined in the implementation section but not in the interface are
431 # included in the documentation. If set to NO only methods in the interface are
438 # extracted and appear in the documentation as a namespace called
448 # members will be included in the various overviews, but no documentation
455 # undocumented classes that are normally visible in the class hierarchy. If set
456 # to NO these classes will be included in the various overviews. This option has
464 # included in the documentation.
484 # names in lower-case letters. If set to YES upper-case letters are also
486 # in case and if your file system supports case sensitive file names. Windows
493 # their full class and namespace scopes in the documentation. If set to YES the
500 # the files that are included by a file in the documentation of that file.
507 # which file to include in order to use the member.
513 # files with double quotes in the documentation rather than with sharp brackets.
518 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
526 # name. If set to NO the members will appear in declaration order.
533 # name. If set to NO the members will appear in declaration order. Note that
534 # this will also influence the order of the classes in the class list.
541 # destructors are listed first. If set to NO the constructors will appear in the
553 # appear in their defined order.
573 # accept a match between prototype and implementation in such cases.
579 # todo list. This list is created by putting \todo commands in the
586 # test list. This list is created by putting \test commands in the
593 # list. This list is created by putting \bug commands in the documentation.
599 # the deprecated list. This list is created by putting \deprecated commands in
612 # initial value of a variable or macro / define can have for it to appear in the
616 # controlled using \showinitializer or \hideinitializer command in the
655 # output files in an output format independent way. To create the layout file
671 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
705 # potential errors in the documentation, such as not documenting some parameters
706 # in a documented function, or documenting parameters that don't exist or using
759 # *.h) to filter out the source-files in the directories. If left blank the
818 # *.h) to filter out the source-files in the directories. If left blank all
831 # that contain images that are to be included in the documentation (see the
891 # Note: To get rid of all source code in the generated output, make sure that
923 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
930 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
941 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
948 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
952 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
953 # tools must be available from the command line (i.e. in the search path).
981 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
988 # In case all classes in a project start with a common prefix, all classes will
989 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1006 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1056 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1076 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1084 # will adjust the colors in the stylesheet and background images according to
1095 # in the HTML output. For a value of 0 the output will use grayscales only. A
1103 # luminance component of the colors in the HTML output. Values below 100
1130 # shown in the various tree structured indices initially; the user can expand
1135 # representing an infinite number of entries and will result in a full expanded
1146 # Makefile in the HTML output directory. Running make will produce the docset in
1147 # that directory and running make install will install the docset in
1195 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1197 # words in the documentation. The HTML workshop also contains a viewer for
1205 # file. You can add a path in front of the file if the result should not be
1220 # YES) or that it should be included in the master .chm file ( NO).
1233 # YES) or a normal table of contents ( NO) in the .chm file.
1311 # install this plugin and make it available under the help contents menu in
1333 # it. Since the tabs in the index contain the same information as the navigation
1358 # doxygen will group on one line in the generated HTML documentation.
1361 # in the overview section.
1368 # to set the initial width (in pixels) of the frame in which the tree is shown.
1375 # external symbols imported via tag files in a separate window.
1381 # Use this tag to change the font size of LaTeX formulas included as images in
1394 # Note that when changing this option you need to delete any form_*.png files in
1404 # installed or if you want to formulas look prettier in the HTML output. When
1520 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1546 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1557 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1573 # trees in general.
1589 # that should be included in the LaTeX output. To get the times font for
1650 # when generating formulas in HTML.
1657 # index chapters (such as File Index, Compound Index, etc.) in the output.
1664 # code with syntax highlighting in the LaTeX output.
1693 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1702 # trees in general.
1730 # Set optional variables used in the generation of an RTF document. Syntax is
1748 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1766 # will generate one additional man file for each entity documented in the real
1785 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1824 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1873 # The names of the make variables in the generated doxyrules.make file are
1874 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
1886 # C-preprocessor directives found in the sources and include files.
1892 # in the source code. If set to NO only conditional compilation will be
1893 # performed. Macro expansion can be done in a controlled way by setting
1908 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
1923 # patterns (like *.h and *.hpp) to filter out the header-files in the
1942 # macro definition that is found in the sources will be used. Use the PREDEFINED
1944 # definition found in the source code.
1973 # the path). If a tag file is not located in the directory in which doxygen is
1984 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
1990 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
1997 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2015 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2025 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2027 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2032 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2033 # then run dia to produce the diagram and insert it in the documentation. The
2035 # If left empty dia is assumed to be found in the default search path.
2048 # Bell Labs. The other options in this section have no effect if this option is
2055 # to run in parallel. When set to 0 doxygen will base this on the number of
2056 # processors available in the system. You can set it explicitly to a value
2066 # sure dot is able to find the font, which can be done by putting it in a
2074 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2113 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2163 # So in most cases it will be better to enable call graphs for selected
2174 # So in most cases it will be better to enable caller graphs for selected
2189 # dependencies a directory has on other directories in a graphical way. The
2191 # files in the directories.
2199 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2200 # to make the SVG files visible in IE 9+ (other browsers do not have this
2213 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2221 # found. If left blank, it is assumed the dot tool can be found in the path.
2227 # contain dot files that are included in the documentation (see the \dotfile
2234 # contain msc files that are included in the documentation (see the \mscfile
2240 # contain dia files that are included in the documentation (see the \diafile
2246 # that will be shown in the graph. If the number of nodes in a graph becomes
2249 # children of the root node in a graph is already larger than
2282 # files in one run (i.e. multiple -o and -T options on the command line). This
2291 # explaining the meaning of the various boxes and arrows in the dot generated