Lines Matching +full:- +full: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.
20 # doxygen -x [configFile]
24 # doxygen -x_noenv [configFile]
26 #---------------------------------------------------------------------------
28 #---------------------------------------------------------------------------
31 # file that follow. The default is UTF-8 which is also the encoding used for all
35 # The default value is: UTF-8.
37 DOXYFILE_ENCODING      = UTF-8
39 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
40 # double-quotes, unless you are using Doxywizard) that should identify the
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
74 # sub-directories (in 2 levels) under the output directory of each output format
76 # option can be useful when feeding doxygen a huge amount of source files, where
79 # control the number of sub-directories.
84 # Controls the number of sub-directories that will be created when
88 # sub-directories are organized in 2 levels, the first level always has a fixed
95 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
96 # characters to appear in the names of generated files. If set to NO, non-ASCII
107 # Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English
109 # Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with
110 # English messages), Korean, Korean-en (Korean with English messages), Latvian,
112 # Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,
126 # description of a member or function before the detailed description
134 # This tag implements a quasi-intelligent brief description abbreviator that is
138 # text. Otherwise, the brief description is used as-is. If left blank, the
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.
178 # Stripping is only done if one of the specified strings matches the left-hand
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
194 # using the -I flag.
200 # support long names like on DOS, Mac, or CD-ROM.
206 # first line (until the first dot) of a Javadoc-style comment as the brief
207 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
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
218 # Javadoc-style will behave just like regular comments and it will not be
225 # line (until the first dot) of a Qt-style comment as the brief description. If
226 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
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
253 # documentation from any documented member that it re-implements.
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
329 # Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,
337 # Note: For files without extension you can use no_extension as a placeholder.
348 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
358 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
368 # classes, or namespaces to their corresponding documentation. Such a link can
369 # be prevented in individual cases by putting a % sign in front of the word or
376 # to include (a tag file for) the STL sources as input, then you should set this
400 # getter and setter methods for a property. Setting this option to YES will make
401 # doxygen to replace the get and set methods by a property in the documentation.
402 # This will only work if the methods are indeed getting or setting a simple
412 # all members of a group must be documented explicitly.
417 # If one adds a struct or class to a group and this option is enabled, then also
425 # (for instance a group of public functions) to be put as a subgroup of that
435 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
448 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
454 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
456 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
457 # with name TypeT. When disabled the typedef will appear as a member of a file,
468 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
471 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
472 # symbols. At the end of a run doxygen will report the cache usage and suggest
473 # the optimal cache size from a speed point of view.
480 # cores available in the system. You can set it explicitly to a value larger
491 #---------------------------------------------------------------------------
493 #---------------------------------------------------------------------------
505 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
512 # methods of a class will be included in the documentation.
523 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
537 # This flag is only useful for Objective-C code. If set to YES, local methods,
546 # extracted and appear in the documentation as a namespace called
554 # If this flag is set to YES, the name of an unnamed parameter in a declaration
585 # documentation blocks found inside the body of a function. If set to NO, these
591 # The INTERNAL_DOCS tag determines if documentation that is typed after a
623 # append additional text to a page's title, such as Class Reference. If set to
629 # If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
635 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
636 # the files that are included by a file in the documentation of that file.
654 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
695 # fully-qualified names, including namespaces. If set to NO, the class list will
705 # type resolution of all parameters of a function it will reject a match between
706 # the prototype and the implementation of a member function even if there is
707 # only one candidate or it is obvious which candidate to choose by doing a
709 # accept a match between prototype and implementation in such cases.
746 # initial value of a variable or macro / define can have for it to appear in the
748 # it will be hidden. Use a value of 0 to hide initializers completely. The
777 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
780 # popen()) the command command input-file, where command is the value of the
781 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
787 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
790 # that represents doxygen's defaults, run doxygen with the -l option. You can
791 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
795 # Note that if you run doxygen from a directory containing a file called
802 # the reference definitions. This must be a list of .bib files. The .bib
811 #---------------------------------------------------------------------------
813 #---------------------------------------------------------------------------
840 # a documented function twice, or documenting parameters that don't exist or
864 # a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
866 # at the end of the doxygen process doxygen will return with a non-zero status.
883 # In the $text part of the WARN_FORMAT command it is possible that a reference
884 # to a more specific place is given. To make it easier to jump to this place
885 # (outside of doxygen) the user can define a custom "cut" / "paste" string.
893 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
896 # warning and error messages are written to standard error. When as file - is
902 #---------------------------------------------------------------------------
904 #---------------------------------------------------------------------------
918 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
923 # The default value is: UTF-8.
925 INPUT_ENCODING         = UTF-8
929 # character encoding on a per file pattern basis. Doxygen will compare the file
931 # INPUT_ENCODING) if there is a match. The character encodings are a list of the
932 # form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding
939 # *.h) to filter out the source-files in the directories.
1003 # excluded from the INPUT source files. This way you can easily exclude a
1004 # subdirectory from a directory tree whose root is specified with the INPUT tag.
1011                          include/ceed/jit-source \
1012                          tests/junit-xml \
1014                          include/ceed-fortran-name.h \
1018 # directories that are symbolic links (a Unix file system feature) are excluded
1035 # output. The symbol name can be a fully qualified name, a word, or if the
1036 # wildcard * is used, a substring. Examples: ANamespace, AClass,
1053 # *.h) to filter out the source-files in the directories. If left blank all
1071 # The INPUT_FILTER tag can be used to specify a program that doxygen should
1075 # <filter> <input-file>
1077 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1088 # commands (so in case of a Windows batch file always use @echo OFF), should be
1097 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1099 # filter if there is a match. The filters are a list of the form: pattern=filter
1118 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1119 # it is also possible to disable source filtering for a specific pattern using
1120 # *.ext= (so without naming a filter).
1125 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1127 # (index.html). This can be useful if you have a project on for instance GitHub
1133 # characters from position 72 are to be considered as comment. A common
1141 #---------------------------------------------------------------------------
1143 #---------------------------------------------------------------------------
1145 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1146 # generated. Documented entities will be cross-referenced with these sources.
1187 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1188 # source code will show a tooltip with additional information such as prototype,
1190 # will make the HTML file larger and loading of large files a bit slower, you
1198 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1204 # - Install the latest version of global
1205 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1206 # - Make sure the INPUT points to the root of the source tree
1207 # - Run doxygen as normal
1219 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1227 #---------------------------------------------------------------------------
1229 #---------------------------------------------------------------------------
1232 # compounds will be generated. Enable this if the project contains a lot of
1238 # In case all classes in a project start with a common prefix, all classes will
1240 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1246 #---------------------------------------------------------------------------
1248 #---------------------------------------------------------------------------
1255 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1270 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1271 # each generated HTML page. If the tag is left blank doxygen will generate a
1276 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1278 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1284 # default header when upgrading to a newer version of doxygen. For a description
1290 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1291 # generated HTML page. If the tag is left blank doxygen will generate a standard
1292 # footer. See HTML_HEADER for more information on how to generate a default
1300 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1301 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1302 # the HTML output. If left blank doxygen will generate a default style sheet.
1312 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1330 # files will be copied as-is; there are no commands or markers available.
1336 # should be rendered with a dark or light theme. Default setting AUTO_LIGHT
1340 # user toggle between dark and light mode via a button.
1346 # dark mode via a button..
1354 # this color. Hue is specified as an angle on a color-wheel, see
1364 # in the HTML output. For a value of 0 the output will use gray-scales only. A
1375 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1383 # documentation will contain a main index with vertical navigation menus that
1404 # such a level that at most the specified number of entries are visible (unless
1405 # a fully collapsed tree already exceeds this amount). So setting the number of
1406 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1407 # representing an infinite number of entries and will result in a full expanded
1418 # create a documentation set, doxygen will generate a Makefile in the HTML
1429 # This tag determines the name of the docset feed. A documentation feed provides
1430 # an umbrella under which multiple documentation sets from a single provider
1431 # (such as a company or product suite) can be grouped.
1437 # This tag determines the URL of the docset feed. A documentation feed provides
1438 # an umbrella under which multiple documentation sets from a single provider
1439 # (such as a company or product suite) can be grouped.
1444 # This tag specifies a string that should uniquely identify the documentation
1445 # set bundle. This should be a reverse domain-name style string, e.g.
1452 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1453 # the documentation publisher. This should be a reverse domain-name style
1468 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1470 # a.o. the download links, offline the HTML help workshop was already many years
1474 # ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).
1476 # The HTML Help Workshop contains a compiler that can convert all HTML output
1477 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1480 # HTML files also contain an index, a table of contents, and you can search for
1481 # words in the documentation. The HTML workshop also contains a viewer for
1489 # file. You can add a path in front of the file if the result should not be
1496 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1503 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1516 # The BINARY_TOC flag controls whether a binary table of contents is generated
1517 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1533 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1550 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1559 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
1565 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1568 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1576 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1583 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1589 # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
1607 # A unique identifier for the Eclipse help plugin. When installing the plugin
1618 # of each HTML page. A value of NO enables the index and the value YES disables
1626 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1628 # value is set to YES, a side panel will be generated containing a tree-like
1630 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1633 # further fine tune the look of the index (see "Fine-tuning the output"). As an
1646 # YES). Setting this to YES gives a layout similar to
1658 # Note that a value of 0 will completely suppress the enum values from appearing
1673 # external symbols imported via tag files in a separate window.
1698 # the HTML documentation. When you change the font size after a successful
1714 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1737 # http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3
1740 # Possible values are: HTML-CSS (which is slower, but has the best
1745 # translated into HTML-CSS) and SVG.
1746 # The default value is: HTML-CSS.
1749 MATHJAX_FORMAT         = HTML-CSS
1757 # MathJax. However, it is strongly recommended to install a local copy of
1759 # - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
1760 # - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
1768 # https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):
1778 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1781 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
1787 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1791 # there is already a search function so this one should typically be disabled.
1793 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1801 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1809 # implemented using a web server instead of a web client using JavaScript. There
1811 # setting. When disabled, doxygen will generate a PHP script for searching and
1837 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1850 # search data is written to a file for indexing by an external tool. With the
1867 # all added to the same external search index. Each project needs to have a
1869 # to a relative location where the documentation can be found. The format is:
1875 #---------------------------------------------------------------------------
1877 #---------------------------------------------------------------------------
1884 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1953 # The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
1955 # first chapter. If it is left blank doxygen will generate a standard header. It
1956 # is highly recommended to start with a default header using
1957 # doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty
1961 # Note: Only use a user-defined header if you know what you are doing!
1963 # default header when upgrading to a newer version of doxygen. The following
1964 # commands have a special meaning inside the header (and footer): For a
1970 # The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
1972 # last chapter. If it is left blank doxygen will generate a standard footer. See
1973 # LATEX_HEADER for more information on how to generate a default footer and what
1976 # normally uses. Note: Only use a user-defined footer if you know what you are
1982 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1995 # directory. Note that the files will be copied as-is; there are no commands or
2004 # makes the output suitable for online browsing using a PDF viewer.
2012 # files. Set this option to YES, to get a higher quality PDF documentation.
2044 # path from which the emoji images will be read. If a relative path is entered,
2051 #---------------------------------------------------------------------------
2053 #---------------------------------------------------------------------------
2062 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
2091 # configuration file, i.e. a series of assignments. You only have to provide
2101 # similar to doxygen's configuration file. A template extensions file can be
2102 # generated using doxygen -e rtf extensionFile.
2107 #---------------------------------------------------------------------------
2109 #---------------------------------------------------------------------------
2117 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2119 # it. A directory man3 will be created inside the directory specified by
2127 # man pages. In case the manual section does not start with a number, the number
2151 #---------------------------------------------------------------------------
2153 #---------------------------------------------------------------------------
2161 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2170 # listings (including syntax highlighting and cross-referencing information) to
2185 #---------------------------------------------------------------------------
2187 #---------------------------------------------------------------------------
2196 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2203 #---------------------------------------------------------------------------
2205 #---------------------------------------------------------------------------
2215 #---------------------------------------------------------------------------
2217 #---------------------------------------------------------------------------
2219 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
2236 # formatted so it can be parsed by a human reader. This is useful if you want to
2253 #---------------------------------------------------------------------------
2255 #---------------------------------------------------------------------------
2258 # C-preprocessor directives found in the sources and include files.
2265 # performed. Macro expansion can be done in a controlled way by setting
2281 # INCLUDE_PATH will be searched if a #include is found.
2296 # patterns (like *.h and *.hpp) to filter out the header-files in the
2304 # defined before the preprocessor is started (similar to the -D option of e.g.
2305 # gcc). The argument of the tag is a list of macros of the form: name or
2307 # is assumed. To prevent a macro definition from being undefined via #undef or
2315 # tag can be used to specify a list of macro names that should be expanded. The
2317 # tag if you want to use a different macro definition that overrules the
2324 # remove all references to function-like macros that are alone on a line, have
2325 # an all uppercase name, and do not end with a semicolon. Such function macros
2326 # are typically used for boiler-plate code, and will confuse the parser if not
2333 #---------------------------------------------------------------------------
2335 #---------------------------------------------------------------------------
2339 # a tag file without this location is as follows:
2346 # Note: Each tag file must have a unique name (where the name does NOT include
2347 # the path). If a tag file is not located in the directory in which doxygen is
2352 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2379 #---------------------------------------------------------------------------
2381 #---------------------------------------------------------------------------
2391 # and usage relations if the target is undocumented or is not a class.
2398 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2407 # processors available in the system. You can set it explicitly to a value
2416 # subgraphs. When you want a differently looking font in the dot files that
2418 # For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node,
2419 # Edge and Graph Attributes specification</a> You need to make sure dot is able
2420 # to find the font, which can be done by putting it in a standard location or by
2429 # add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a
2431 # arrows shapes.</a>
2438 # around nodes set 'shape=plain' or 'shape=plaintext' <a
2439 # href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a>
2451 # If the CLASS_GRAPH tag is set to YES (or GRAPH) then doxygen will generate a
2454 # otherwise the built-in generator will be used. If the CLASS_GRAPH tag is set
2462 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2471 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2480 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2514 # to display on a single line. If the actual line length exceeds this threshold
2531 # YES then doxygen will generate a graph for each documented file showing the
2540 # set to YES then doxygen will generate a graph for each documented file showing
2548 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2551 # Note that enabling this option will significantly increase the time of a run.
2553 # functions only using the \callgraph command. Disabling a call graph can be
2560 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2563 # Note that enabling this option will significantly increase the time of a run.
2565 # functions only using the \callergraph command. Disabling a caller graph can be
2573 # hierarchy of all classes instead of a textual one.
2580 # dependencies a directory has on other directories in a graphical way. The
2613 # Note that this requires a modern browser other than Internet Explorer. Tested
2650 # a preprocessing step. Doxygen will generate a warning when it encounters a
2655 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2661 # the !include statement in a plantuml block.
2666 # that will be shown in the graph. If the number of nodes in a graph becomes
2668 # by representing a node as a red box. Note that doxygen if the number of direct
2669 # children of the root node in a graph is already larger than
2671 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2678 # generated by dot. A depth value of 3 means that only nodes reachable from the
2679 # root by following a path via at most 3 edges will be shown. Nodes that lay
2682 # note that the size of a graph can be further restricted by
2683 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2690 # files in one run (i.e. multiple -o and -T options on the command line). This
2698 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page