Lines Matching refs:a

4 # doxygen (www.doxygen.org) for a project.
6 # All text after a double hash (##) is considered a comment and is placed in
9 # All text after a single hash (#) is considered a comment and will be ignored.
39 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
42 # title of most generated pages and in a few other places.
47 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
54 # for a project that appears at the top of each page and should give viewer a
59 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
67 # into which the generated documentation will be written. If a relative path is
76 # option can be useful when feeding doxygen a huge amount of source files, where
88 # sub-directories are organized in 2 levels, the first level always has a fixed
126 # description of a member or function before the detailed description
134 # This tag implements a quasi-intelligent brief description abbreviator that is
141 # specifies, contains, represents, a, an and the.
151                          a \
156 # doxygen will generate a detailed section even if there is only a brief
163 # inherited members of a class in the documentation of that class as if those
177 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
189 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
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
206 # first line (until the first dot) of a Javadoc-style comment as the brief
208 # style comments (thus requiring an explicit @brief command for a brief
214 # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
217 # as being the beginning of a Javadoc-style comment "banner". If set to NO, the
225 # line (until the first dot) of a Qt-style comment as the brief description. If
227 # requiring an explicit \brief command for a brief description.)
232 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
233 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
234 # a brief description. This used to be the default behavior. The new default is
235 # to treat a multi-line C++ comment block as a detailed description. Set this
258 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
259 # page for each member. If set to NO, the documentation of a member will be part
265 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
271 # This tag can be used to specify a number of aliases that act as commands in
277 # documentation, which will result in a user-defined paragraph with heading
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
282 # have to escape them by means of a backslash (\), this can lead to conflicts
284 # @} or use a double escape (\\{ and \\})
325 # parses. With this tag you can assign which parser to use for a given
326 # extension. Doxygen has a built-in mapping, but you can override or extend it
327 # using this tag. The format is ext=language, where ext is a file extension, and
337 # Note: For files without extension you can use no_extension as a placeholder.
357 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
369 # Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a
378 # classes, or namespaces to their corresponding documentation. Such a link can
379 # be prevented in individual cases by putting a % sign in front of the word or
386 # to include (a tag file for) the STL sources as input, then you should set this
410 # getter and setter methods for a property. Setting this option to YES will make
411 # doxygen to replace the get and set methods by a property in the documentation.
412 # This will only work if the methods are indeed getting or setting a simple
422 # all members of a group must be documented explicitly.
427 # If one adds a struct or class to a group and this option is enabled, then also
435 # (for instance a group of public functions) to be put as a subgroup of that
445 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
458 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
464 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
466 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
467 # with name TypeT. When disabled the typedef will appear as a member of a file,
478 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
481 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
482 # symbols. At the end of a run doxygen will report the cache usage and suggest
483 # the optimal cache size from a speed point of view.
490 # cores available in the system. You can set it explicitly to a value larger
523 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
530 # methods of a class will be included in the documentation.
541 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
564 # extracted and appear in the documentation as a namespace called
572 # If this flag is set to YES, the name of an unnamed parameter in a declaration
604 # documentation blocks found inside the body of a function. If set to NO, these
610 # The INTERNAL_DOCS tag determines if documentation that is typed after a
642 # append additional text to a page's title, such as Class Reference. If set to
648 # If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
654 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
655 # the files that are included by a file in the documentation of that file.
673 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
724 # type resolution of all parameters of a function it will reject a match between
725 # the prototype and the implementation of a member function even if there is
726 # only one candidate or it is obvious which candidate to choose by doing a
728 # accept a match between prototype and implementation in such cases.
765 # initial value of a variable or macro / define can have for it to appear in the
767 # it will be hidden. Use a value of 0 to hide initializers completely. The
796 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
806 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
810 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
814 # Note that if you run doxygen from a directory containing a file called
821 # the reference definitions. This must be a list of .bib files. The .bib
859 # a documented function twice, or documenting parameters that don't exist or
891 # a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
893 # at the end of the doxygen process doxygen will return with a non-zero status.
897 # of a run, in case a WARN_LOGFILE is defined the warning messages will be
898 # besides being in the defined file also be shown at the end of a run, unless
917 # In the $text part of the WARN_FORMAT command it is possible that a reference
918 # to a more specific place is given. To make it easier to jump to this place
919 # (outside of doxygen) the user can define a custom "cut" / "paste" string.
927 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
961 # character encoding on a per file pattern basis. Doxygen will compare the file
963 # INPUT_ENCODING) if there is a match. The character encodings are a list of the
1035 # excluded from the INPUT source files. This way you can easily exclude a
1036 # subdirectory from a directory tree whose root is specified with the INPUT tag.
1044 # directories that are symbolic links (a Unix file system feature) are excluded
1061 # output. The symbol name can be a fully qualified name, a word, or if the
1062 # wildcard * is used, a substring. Examples: ANamespace, AClass,
1093 # The INPUT_FILTER tag can be used to specify a program that doxygen should
1110 # commands (so in case of a Windows batch file always use @echo OFF), should be
1119 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1121 # filter if there is a match. The filters are a list of the form: pattern=filter
1141 # it is also possible to disable source filtering for a specific pattern using
1142 # *.ext= (so without naming a filter).
1147 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1149 # (index.html). This can be useful if you have a project on for instance GitHub
1167 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1209 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1210 # source code will show a tooltip with additional information such as prototype,
1212 # will make the HTML file larger and loading of large files a bit slower, you
1241 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1254 # compounds will be generated. Enable this if the project contains a lot of
1260 # The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)
1278 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1293 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1294 # each generated HTML page. If the tag is left blank doxygen will generate a
1299 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1307 # default header when upgrading to a newer version of doxygen. For a description
1313 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1314 # generated HTML page. If the tag is left blank doxygen will generate a standard
1315 # footer. See HTML_HEADER for more information on how to generate a default
1323 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1325 # the HTML output. If left blank doxygen will generate a default style sheet.
1364 # should be rendered with a dark or light theme.
1370 # light and dark mode via a button.
1378 # this color. Hue is specified as an angle on a color-wheel, see
1388 # in the HTML output. For a value of 0 the output will use gray-scales only. A
1399 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1407 # documentation will contain a main index with vertical navigation menus that
1435 # such a level that at most the specified number of entries are visible (unless
1436 # a fully collapsed tree already exceeds this amount). So setting the number of
1437 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1438 # representing an infinite number of entries and will result in a full expanded
1449 # create a documentation set, doxygen will generate a Makefile in the HTML
1461 # an umbrella under which multiple documentation sets from a single provider
1462 # (such as a company or product suite) can be grouped.
1469 # an umbrella under which multiple documentation sets from a single provider
1470 # (such as a company or product suite) can be grouped.
1475 # This tag specifies a string that should uniquely identify the documentation
1476 # set bundle. This should be a reverse domain-name style string, e.g.
1483 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1484 # the documentation publisher. This should be a reverse domain-name style
1499 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1501 # a.o. the download links, offline the HTML help workshop was already many years
1507 # The HTML Help Workshop contains a compiler that can convert all HTML output
1508 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1511 # HTML files also contain an index, a table of contents, and you can search for
1512 # words in the documentation. The HTML workshop also contains a viewer for
1520 # file. You can add a path in front of the file if the result should not be
1534 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1547 # The BINARY_TOC flag controls whether a binary table of contents is generated
1548 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1574 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1606 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1667 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1669 # value is set to YES, a side panel will be generated containing a tree-like
1671 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1687 # YES). Setting this to YES gives a layout similar to
1699 # Note that a value of 0 will completely suppress the enum values from appearing
1714 # external symbols imported via tag files in a separate window.
1739 # the HTML documentation. When you change the font size after a successful
1798 # MathJax. However, it is strongly recommended to install a local copy of
1819 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1828 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1832 # there is already a search function so this one should typically be disabled.
1834 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1842 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1850 # implemented using a web server instead of a web client using JavaScript. There
1852 # setting. When disabled, doxygen will generate a PHP script for searching and
1878 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1891 # search data is written to a file for indexing by an external tool. With the
1908 # all added to the same external search index. Each project needs to have a
1910 # to a relative location where the documentation can be found. The format is:
1925 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1994 # The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
1996 # first chapter. If it is left blank doxygen will generate a standard header. It
1997 # is highly recommended to start with a default header using
2002 # Note: Only use a user-defined header if you know what you are doing!
2004 # default header when upgrading to a newer version of doxygen. The following
2005 # commands have a special meaning inside the header (and footer): For a
2011 # The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
2013 # last chapter. If it is left blank doxygen will generate a standard footer. See
2014 # LATEX_HEADER for more information on how to generate a default footer and what
2017 # normally uses. Note: Only use a user-defined footer if you know what you are
2045 # makes the output suitable for online browsing using a PDF viewer.
2053 # files. Set this option to YES, to get a higher quality PDF documentation.
2065 # keyboard input (\read on a not open input stream) cause the job to abort,
2092 # path from which the emoji images will be read. If a relative path is entered,
2110 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
2139 # configuration file, i.e. a series of assignments. You only have to provide
2165 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2175 # man pages. In case the manual section does not start with a number, the number
2209 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2244 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2267 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
2284 # formatted so it can be parsed by a human reader. This is useful if you want to
2313 # performed. Macro expansion can be done in a controlled way by setting
2329 # INCLUDE_PATH will be searched if a #include is found.
2353 # gcc). The argument of the tag is a list of macros of the form: name or
2355 # is assumed. To prevent a macro definition from being undefined via #undef or
2365 # tag can be used to specify a list of macro names that should be expanded. The
2367 # tag if you want to use a different macro definition that overrules the
2374 # remove all references to function-like macros that are alone on a line, have
2375 # an all uppercase name, and do not end with a semicolon. Such function macros
2389 # a tag file without this location is as follows:
2396 # Note: Each tag file must have a unique name (where the name does NOT include
2397 # the path). If a tag file is not located in the directory in which doxygen is
2402 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2434 # and usage relations if the target is undocumented or is not a class.
2441 # https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2450 # processors available in the system. You can set it explicitly to a value
2459 # subgraphs. When you want a differently looking font in the dot files that
2461 # For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node,
2462 # Edge and Graph Attributes specification</a> You need to make sure dot is able
2463 # to find the font, which can be done by putting it in a standard location or by
2472 # add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a
2474 # arrows shapes.</a>
2481 # around nodes set 'shape=plain' or 'shape=plaintext' <a
2482 # href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a>
2495 # generate a graph for each documented class showing the direct and indirect
2507 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2510 # class with other documented classes. Explicit enabling a collaboration graph,
2512 # command \collaborationgraph. Disabling a collaboration graph can be
2519 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2520 # groups, showing the direct groups dependencies. Explicit enabling a group
2522 # of the command \groupgraph. Disabling a directory graph can be accomplished by
2531 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2565 # to display on a single line. If the actual line length exceeds this threshold
2582 # YES then doxygen will generate a graph for each documented file showing the
2593 # set to YES then doxygen will generate a graph for each documented file showing
2604 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2607 # Note that enabling this option will significantly increase the time of a run.
2609 # functions only using the \callgraph command. Disabling a call graph can be
2616 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2619 # Note that enabling this option will significantly increase the time of a run.
2621 # functions only using the \callergraph command. Disabling a caller graph can be
2629 # hierarchy of all classes instead of a textual one.
2636 # dependencies a directory has on other directories in a graphical way. The
2638 # files in the directories. Explicit enabling a directory graph, when
2640 # \directorygraph. Disabling a directory graph can be accomplished by means of
2672 # Note that this requires a modern browser other than Internet Explorer. Tested
2710 # a preprocessing step. Doxygen will generate a warning when it encounters a
2715 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2721 # the !include statement in a plantuml block.
2726 # that will be shown in the graph. If the number of nodes in a graph becomes
2728 # by representing a node as a red box. Note that doxygen if the number of direct
2729 # children of the root node in a graph is already larger than
2731 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2739 # root by following a path via at most 3 edges will be shown. Nodes that lay
2742 # note that the size of a graph can be further restricted by
2743 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2758 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2779 # use a built-in version of mscgen tool to produce the charts. Alternatively,