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.
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
32 # title of most generated pages and in a few other places.
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
44 # for a project that appears at the top of each page and should give viewer a
49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
57 # into which the generated documentation will be written. If a relative path is
66 # option can be useful when feeding doxygen a huge amount of source files, where
104 # description of a member or function before the detailed description
112 # This tag implements a quasi-intelligent brief description abbreviator that is
119 # specifies, contains, represents, a, an and the.
124 # doxygen will generate a detailed section even if there is only a brief
131 # inherited members of a class in the documentation of that class as if those
145 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
157 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
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
174 # first line (until the first dot) of a Javadoc-style comment as the brief
176 # style comments (thus requiring an explicit @brief command for a brief
183 # line (until the first dot) of a Qt-style comment as the brief description. If
185 # requiring an explicit \brief command for a brief description.)
190 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
191 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
192 # a brief description. This used to be the default behavior. The new default is
193 # to treat a multi-line C++ comment block as a detailed description. Set this
208 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
209 # page for each member. If set to NO, the documentation of a member will be part
215 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
221 # This tag can be used to specify a number of aliases that act as commands in
227 # documentation, which will result in a user-defined paragraph with heading
233 # This tag can be used to specify a number of word-keyword mappings (TCL only).
268 # parses. With this tag you can assign which parser to use for a given
269 # extension. Doxygen has a built-in mapping, but you can override or extend it
270 # using this tag. The format is ext=language, where ext is a file extension, and
279 # Note: For files without extension you can use no_extension as a placeholder.
297 # classes, or namespaces to their corresponding documentation. Such a link can
298 # be prevented in individual cases by putting a % sign in front of the word or
305 # to include (a tag file for) the STL sources as input, then you should set this
329 # getter and setter methods for a property. Setting this option to YES will make
330 # doxygen to replace the get and set methods by a property in the documentation.
331 # This will only work if the methods are indeed getting or setting a simple
341 # all members of a group must be documented explicitly.
346 # If one adds a struct or class to a group and this option is enabled, then also
354 # (for instance a group of public functions) to be put as a subgroup of that
364 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
377 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
383 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
385 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
386 # with name TypeT. When disabled the typedef will appear as a member of a file,
397 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
400 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
401 # symbols. At the end of a run doxygen will report the cache usage and suggest
402 # the optimal cache size from a speed point of view.
421 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
433 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
456 # extracted and appear in the documentation as a namespace called
488 # documentation blocks found inside the body of a function. If set to NO, these
494 # The INTERNAL_DOCS tag determines if documentation that is typed after a
518 # append additional text to a page's title, such as Class Reference. If set to
524 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
525 # the files that are included by a file in the documentation of that file.
543 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
594 # type resolution of all parameters of a function it will reject a match between
595 # the prototype and the implementation of a member function even if there is
596 # only one candidate or it is obvious which candidate to choose by doing a
598 # accept a match between prototype and implementation in such cases.
635 # initial value of a variable or macro / define can have for it to appear in the
637 # it will be hidden. Use a value of 0 to hide initializers completely. The
666 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
676 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
680 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
683 # Note that if you run doxygen from a directory containing a file called
690 # the reference definitions. This must be a list of .bib files. The .bib
728 # in a documented function, or documenting parameters that don't exist or using
743 # a warning is encountered.
758 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
808 # excluded from the INPUT source files. This way you can easily exclude a
809 # subdirectory from a directory tree whose root is specified with the INPUT tag.
817 # directories that are symbolic links (a Unix file system feature) are excluded
834 # output. The symbol name can be a fully qualified name, a word, or if the
835 # wildcard * is used, a substring. Examples: ANamespace, AClass,
869 # The INPUT_FILTER tag can be used to specify a program that doxygen should
890 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
892 # filter if there is a match. The filters are a list of the form: pattern=filter
912 # it is also possible to disable source filtering for a specific pattern using
913 # *.ext= (so without naming a filter).
918 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
920 # (index.html). This can be useful if you have a project on for instance GitHub
929 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
971 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
972 # source code will show a tooltip with additional information such as prototype,
974 # will make the HTML file larger and loading of large files a bit slower, you
1003 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1016 # compounds will be generated. Enable this if the project contains a lot of
1029 # In case all classes in a project start with a common prefix, all classes will
1031 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1046 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1061 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1062 # each generated HTML page. If the tag is left blank doxygen will generate a
1067 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1075 # default header when upgrading to a newer version of doxygen. For a description
1081 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1082 # generated HTML page. If the tag is left blank doxygen will generate a standard
1083 # footer. See HTML_HEADER for more information on how to generate a default
1091 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1093 # the HTML output. If left blank doxygen will generate a default style sheet.
1128 # this color. Hue is specified as an angle on a colorwheel, see
1138 # in the HTML output. For a value of 0 the output will use grayscales only. A
1149 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1176 # such a level that at most the specified number of entries are visible (unless
1177 # a fully collapsed tree already exceeds this amount). So setting the number of
1178 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1179 # representing an infinite number of entries and will result in a full expanded
1189 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1201 # an umbrella under which multiple documentation sets from a single provider
1202 # (such as a company or product suite) can be grouped.
1208 # This tag specifies a string that should uniquely identify the documentation
1209 # set bundle. This should be a reverse domain-name style string, e.g.
1216 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1217 # the documentation publisher. This should be a reverse domain-name style
1232 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1236 # The HTML Help Workshop contains a compiler that can convert all HTML output
1237 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1240 # HTML files also contain an index, a table of contents, and you can search for
1241 # words in the documentation. The HTML workshop also contains a viewer for
1249 # file. You can add a path in front of the file if the result should not be
1263 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1276 # The BINARY_TOC flag controls whether a binary table of contents is generated
1277 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1293 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1324 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1385 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1387 # value is set to YES, a side panel will be generated containing a tree-like
1389 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1405 # Note that a value of 0 will completely suppress the enum values from appearing
1420 # external symbols imported via tag files in a separate window.
1427 # the HTML documentation. When you change the font size after a successful
1473 # MathJax. However, it is strongly recommended to install a local copy of
1487 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1495 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1499 # there is already a search function so this one should typically be disabled.
1501 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1509 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1517 # implemented using a web server instead of a web client using Javascript. There
1519 # setting. When disabled, doxygen will generate a PHP script for searching and
1544 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1556 # search data is written to a file for indexing by an external tool. With the
1573 # all added to the same external search index. Each project needs to have a
1575 # to a relative location where the documentation can be found. The format is:
1590 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1645 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1647 # chapter. If it is left blank doxygen will generate a standard header. See
1649 # default header to a separate file.
1651 # Note: Only use a user-defined header if you know what you are doing! The
1652 # following commands have a special meaning inside the header: $title,
1661 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1663 # chapter. If it is left blank doxygen will generate a standard footer. See
1664 # LATEX_HEADER for more information on how to generate a default footer and what
1667 # Note: Only use a user-defined footer if you know what you are doing!
1694 # makes the output suitable for online browsing using a PDF viewer.
1701 # the PDF file directly from the LaTeX files. Set this option to YES, to get a
1761 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1790 # file, i.e. a series of assignments. You only have to provide replacements,
1826 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1836 # man pages. In case the manual section does not start with a number, the number
1870 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1898 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1930 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
1947 # formatted so it can be parsed by a human reader. This is useful if you want to
1976 # performed. Macro expansion can be done in a controlled way by setting
1992 # INCLUDE_PATH will be searched if a #include is found.
2015 # gcc). The argument of the tag is a list of macros of the form: name or
2017 # is assumed. To prevent a macro definition from being undefined via #undef or
2024 # tag can be used to specify a list of macro names that should be expanded. The
2026 # tag if you want to use a different macro definition that overrules the
2033 # remove all references to function-like macros that are alone on a line, have
2034 # an all uppercase name, and do not end with a semicolon. Such function macros
2048 # a tag file without this location is as follows:
2055 # Note: Each tag file must have a unique name (where the name does NOT include
2056 # the path). If a tag file is not located in the directory in which doxygen is
2061 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2098 # If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
2124 # and usage relations if the target is undocumented or is not a class.
2131 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2140 # processors available in the system. You can set it explicitly to a value
2148 # When you want a differently looking font in the dot files that doxygen
2150 # sure dot is able to find the font, which can be done by putting it in a
2166 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2172 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2180 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2189 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2197 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2226 # YES then doxygen will generate a graph for each documented file showing the
2235 # set to YES then doxygen will generate a graph for each documented file showing
2243 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2246 # Note that enabling this option will significantly increase the time of a run.
2248 # functions only using the \callgraph command. Disabling a call graph can be
2255 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2258 # Note that enabling this option will significantly increase the time of a run.
2260 # functions only using the \callergraph command. Disabling a caller graph can be
2268 # hierarchy of all classes instead of a textual one.
2275 # dependencies a directory has on other directories in a graphical way. The
2301 # Note that this requires a modern browser other than Internet Explorer. Tested
2337 # PlantUML is not used or called during a preprocessing step. Doxygen will
2338 # generate a warning when it encounters a \startuml command in this case and
2344 # the !include statement in a plantuml block.
2349 # that will be shown in the graph. If the number of nodes in a graph becomes
2351 # by representing a node as a red box. Note that doxygen if the number of direct
2352 # children of the root node in a graph is already larger than
2354 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2362 # root by following a path via at most 3 edges will be shown. Nodes that lay
2365 # note that the size of a graph can be further restricted by
2366 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2372 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2377 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2393 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page