Lines Matching refs:in

6 # All text after a double hash (##) is considered a comment and is placed in
30 # This tag specifies the encoding used for all characters in the configuration
41 # project for which the documentation is generated. This name is used in the
42 # title of most generated pages and in a few other places.
60 # in the documentation. The maximum height of the logo should not exceed 55
74 # sub-directories (in 2 levels) under the output directory of each output format
77 # putting all generated files in the same directory would otherwise causes
86 # level increment doubles the number of directories, resulting in 4096
88 # sub-directories are organized in 2 levels, the first level always has a fixed
96 # characters to appear in the names of generated files. If set to NO, non-ASCII
103 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
105 # information to generate all constant output in the proper language.
119 # descriptions after the members that are listed in the file and class
135 # used to form the text in various listings. Each string in this list, if found
163 # inherited members of a class in the documentation of that class as if those
171 # before files name in the file list and in the header files. If set to NO the
179 # part of the path. The tag can be used to show relative paths in the file list.
190 # path mentioned in the documentation of a class, which tells the reader which
191 # header file to include in order to use a class. If left blank only the name of
265 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
266 # uses this value to replace tabs by spaces in code fragments.
271 # This tag can be used to specify a number of aliases that act as commands in
276 # will allow you to put the command \sideeffect (or @sideeffect) in the
277 # documentation, which will result in a user-defined paragraph with heading
278 # "Side Effects:". Note that you cannot put \n's in the value part of an alias
279 # to insert newlines (in the resulting output). You can put ^^ in the value part
280 # of an alias to insert a newline as if a physical newline was in the original
281 # file. When you need a literal { or } or , in the value part of an alias you
326 # extension. Doxygen has a built-in mapping, but you can override or extend it
351 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
358 # to that level are automatically included in the table of contents, even if
368 # be prevented in individual cases by putting a % sign in front of the word or
376 # tag to YES in order to let doxygen match functions declarations and
400 # doxygen to replace the get and set methods by a property in the documentation.
408 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
410 # member in the group (if any) for the other members of the group. By default
433 # are shown inside the group in which they are included (e.g. using \ingroup)
437 # Note that this feature does not work in combination with
444 # with only public data fields or simple typedef fields will be shown inline in
445 # the documentation of the scope in which they are defined (i.e. file,
455 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
458 # useful for C code in case the coding convention dictates that all compound
466 # an expensive process and often the same symbol appears multiple times in the
479 # cores available in the system. You can set it explicitly to a value larger
484 # encounter. Generating dot graphs in parallel is controlled by the
494 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
505 # be included in the documentation.
511 # methods of a class will be included in the documentation.
517 # scope will be included in the documentation.
523 # included in the documentation.
529 # locally in source files will be included in the documentation. If set to NO,
530 # only classes defined in header files are included. Does not have any effect
537 # which are defined in the implementation section but not in the interface are
538 # included in the documentation. If set to NO, only methods in the interface are
545 # extracted and appear in the documentation as a namespace called
553 # If this flag is set to YES, the name of an unnamed parameter in a declaration
555 # parameters remain unnamed in the output.
562 # members will be included in the various overviews, but no documentation
569 # undocumented classes that are normally visible in the class hierarchy. If set
570 # to NO, these classes will be included in the various overviews. This option
578 # declarations. If set to NO, these declarations will be included in the
600 # filesystem is case sensitive (i.e. it supports files in the same directory
601 # whose names only differ in casing), the option must be set to YES to properly
602 # deal with such files in case they appear in the input. For filesystems that
604 # output files written for symbols that only differ in casing, such as for two
616 # their full class and namespace scopes in the documentation. If set to YES, the
636 # the files that are included by a file in the documentation of that file.
643 # which file to include in order to use the member.
649 # files with double quotes in the documentation rather than with sharp brackets.
654 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
662 # name. If set to NO, the members will appear in declaration order.
669 # name. If set to NO, the members will appear in declaration order. Note that
670 # this will also influence the order of the classes in the class list.
677 # destructors are listed first. If set to NO the constructors will appear in the
689 # appear in their defined order.
709 # accept a match between prototype and implementation in such cases.
715 # list. This list is created by putting \todo commands in the documentation.
721 # list. This list is created by putting \test commands in the documentation.
727 # list. This list is created by putting \bug commands in the documentation.
733 # the deprecated list. This list is created by putting \deprecated commands in
746 # initial value of a variable or macro / define can have for it to appear in the
750 # controlled using \showinitializer or \hideinitializer command in the
789 # output files in an output format independent way. To create the layout file
806 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
839 # potential errors in the documentation, such as documenting some parameters in
944 # *.h) to filter out the source-files in the directories.
1057 # *.h) to filter out the source-files in the directories. If left blank all
1070 # that contain images that are to be included in the documentation (see the
1092 # commands (so in case of a Windows batch file always use @echo OFF), should be
1152 # Note: To get rid of all source code in the generated output, make sure that
1184 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
1191 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1202 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1209 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1213 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1214 # tools must be available from the command line (i.e. in the search path).
1244 # tag works for classes, function and member names. The entity will be placed in
1261 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1311 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1324 # style sheet in the list overrules the setting of the previous ones in the
1326 # Note: Since the styling of scrollbars can currently not be overruled in
1338 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1359 # will adjust the colors in the style sheet and background images according to
1370 # in the HTML output. For a value of 0 the output will use gray-scales only. A
1378 # luminance component of the colors in the HTML output. Values below 100
1400 # consists of multiple levels of tabs that are statically embedded in every HTML
1417 # shown in the various tree structured indices initially; the user can expand
1422 # representing an infinite number of entries and will result in a full expanded
1433 # create a documentation set, doxygen will generate a Makefile in the HTML
1434 # output directory. Running make will produce the docset in that directory and
1435 # running make install will install the docset in
1486 # in maintenance mode). You can download the HTML help workshop from the web
1494 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1496 # words in the documentation. The HTML workshop also contains a viewer for
1504 # file. You can add a path in front of the file if the result should not be
1519 # (YES) or that it should be included in the main .chm file (NO).
1532 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1612 # install this plugin and make it available under the help contents menu in
1634 # it. Since the tabs in the index contain the same information as the navigation
1671 # doxygen will group on one line in the generated HTML documentation.
1674 # in the overview section.
1681 # to set the initial width (in pixels) of the frame in which the tree is shown.
1688 # external symbols imported via tag files in a separate window.
1712 # Use this tag to change the font size of LaTeX formulas included as images in
1722 # to create new LaTeX commands to be used in formulas as building blocks. See
1730 # installed or if you want to formulas look prettier in the HTML output. When
1774 # - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
1775 # - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
1873 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1899 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1910 # USE_PDFLATEX the default is pdflatex and when in the later case latex is
1920 # Note: This tag is used in the Makefile / make.bat.
1921 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1930 # it will be automatically added in the LaTeX code.
1931 # Note: This tag is used in the generated output file (.tex).
1932 # See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
1940 # trees in general.
1956 # that should be included in the LaTeX output. The package can be specified just
2001 # style sheet in the list overrules the setting of the previous ones in the
2043 # index chapters (such as File Index, Compound Index, etc.) in the output.
2085 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2094 # trees in general.
2122 # Set optional variables used in the generation of an RTF document. Syntax is
2140 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2158 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2165 # will generate one additional man file for each entity documented in the real
2184 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2201 # namespace members in file scope as well, matching the HTML output.
2218 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2267 # The names of the make variables in the generated doxyrules.make file are
2268 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2280 # C-preprocessor directives found in the sources and include files.
2286 # in the source code. If set to NO, only conditional compilation will be
2287 # performed. Macro expansion can be done in a controlled way by setting
2302 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2318 # patterns (like *.h and *.hpp) to filter out the header-files in the
2337 # macro definition that is found in the sources will be used. Use the PREDEFINED
2339 # definition found in the source code.
2368 # the path). If a tag file is not located in the directory in which doxygen is
2379 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2387 # in the modules index. If set to NO, only the current project's groups will be
2393 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2404 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2405 # then run dia to produce the diagram and insert it in the documentation. The
2407 # If left empty dia is assumed to be found in the default search path.
2420 # Bell Labs. The other options in this section have no effect if this option is
2427 # to run in parallel. When set to 0 doxygen will base this on the number of
2428 # processors available in the system. You can set it explicitly to a value
2437 # subgraphs. When you want a differently looking font in the dot files that
2441 # to find the font, which can be done by putting it in a standard location or by
2466 # You can set the path where dot can find font specified with fontname in
2475 # otherwise the built-in generator will be used. If the CLASS_GRAPH tag is set
2494 # in the manual.
2501 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2522 # methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
2524 # methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen
2525 # will not generate fields with class member information in the UML graphs. The
2573 # So in most cases it will be better to enable call graphs for selected
2585 # So in most cases it will be better to enable caller graphs for selected
2601 # dependencies a directory has on other directories in a graphical way. The
2603 # files in the directories.
2610 # of child directories generated in directory dependency graphs by dot.
2618 # output formats in the documentation of the dot tool (Graphviz (see:
2620 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2621 # to make the SVG files visible in IE 9+ (other browsers do not have this
2636 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2644 # found. If left blank, it is assumed the dot tool can be found in the path.
2650 # contain dot files that are included in the documentation (see the \dotfile
2657 # contain msc files that are included in the documentation (see the \mscfile
2663 # contain dia files that are included in the documentation (see the \diafile
2672 # \startuml command in this case and will not generate output for the diagram.
2682 # the !include statement in a plantuml block.
2687 # that will be shown in the graph. If the number of nodes in a graph becomes
2690 # children of the root node in a graph is already larger than
2711 # files in one run (i.e. multiple -o and -T options on the command line). This
2720 # explaining the meaning of the various boxes and arrows in the dot generated