Lines Matching refs:a
10 # with the License. You may obtain a copy of the License at
24 # doxygen (www.doxygen.org) for a project
26 # All text after a hash (#) is considered a comment and will be ignored
37 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
42 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
50 # If a relative path is entered, it will be relative to the location
58 # Enabling this option can be useful when feeding doxygen a huge amount of
79 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
81 # whereas setting the tag to NO uses a Unix-style encoding (the default for
94 # the brief description of a member or function before the detailed description.
100 # This tag implements a quasi-intelligent brief description abbreviator
108 # "represents" "a" "an" "the"
113 # Doxygen will generate a detailed section even if there is only a brief
119 # inherited members of a class in the documentation of that class as if those
132 # can be used to strip a user-defined part of the path. Stripping is
140 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
141 # the path mentioned in the documentation of a class, which tells
142 # the reader which header file to include in order to use a class.
156 # will interpret the first line (until the first dot) of a JavaDoc-style
159 # explicit @brief command for a brief description.
164 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
165 # comments) as a brief description. This used to be the default behaviour.
166 # The new default is to treat a multi-line C++ comment block as a detailed
185 # a new page for each member. If set to NO, the documentation of a member will
190 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
195 # This tag can be used to specify a number of aliases that acts
199 # will result in a user-defined paragraph with heading "Side Effects:".
219 # include (a tag file for) the STL sources as input, then you should
230 # all members of a group must be documented explicitly.
235 # the same type (for instance a group of public functions) to be put as a
253 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
258 # If the EXTRACT_STATIC tag is set to YES all static members of a file
299 # documentation blocks found inside the body of a function.
306 # that is typed after a \internal command is included. If the tag is set
327 # will put a list of the files that are included by a file in the documentation
332 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
391 # the initial value of a variable or define consists of for it to appear in
393 # here it will be hidden. Use a value of 0 to hide initializers completely.
412 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
445 # parameters in a documented function, or documenting parameters that
467 # The WARN_LOGFILE tag can be used to specify a file to which warning
500 # excluded from the INPUT source files. This way you can easily exclude a
501 # subdirectory from a directory tree whose root is specified with the INPUT tag.
506 # directories that are symbolic links (a Unix filesystem feature) are excluded
545 # The INPUT_FILTER tag can be used to specify a program that doxygen should
555 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
557 # filter if there is a match. The filters are a list of the form:
574 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
613 # will generate a verbatim copy of the header file for each class for
624 # contains a lot of classes, structs, unions or interfaces.
630 # in which this list will be split (can be a number in the range [1..20])
634 # In case all classes in a project start with a common prefix, all
651 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
662 # The HTML_HEADER tag can be used to specify a personal HTML header for
663 # each generated HTML page. If it is left blank doxygen will generate a
668 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
669 # each generated HTML page. If it is left blank doxygen will generate a
674 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
677 # will generate a default style sheet. Note that doxygen will try to copy
685 # NO a bullet list will be used.
691 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
698 # can add a path in front of the file if the result should not be
711 # controls if a separate .chi index file is generated (YES) or that
717 # controls whether a binary table of contents is generated (YES) or a
738 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
739 # generated containing a tree-like index structure (just like the one that
740 # is generated for HTML Help). For this to work a browser that supports
763 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
796 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
798 # the first chapter. If it is left blank doxygen will generate a
806 # This makes the output suitable for online browsing using a pdf viewer.
811 # plain latex in the generated Makefile. Set this option to YES to get a
840 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
861 # config file, i.e. a series of assignments. You only have to provide
881 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
910 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
916 # which can be used by a validating XML parser to check the
922 # which can be used by a validating XML parser to check the
951 # generate a Perl module file that captures the structure of
965 # nicely formatted so it can be parsed by a human reader. This is useful
991 # compilation will be performed. Macro expansion can be done in a controlled
1003 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1022 # gcc). The argument of the tag is a list of macros of the form: name
1024 # omitted =1 is assumed. To prevent a macro definition from being
1031 # this tag can be used to specify a list of macro names that should be expanded.
1033 # Use the PREDEFINED tag if you want to use a different macro definition.
1039 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1051 # can be added for each tagfile. The format of a tag file without
1057 # URLs. If a location is present for each tag, the installdox tool
1059 # Note that each tag file must have a unique name
1061 # If a tag file is not located in the directory in which doxygen
1066 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1067 # a tag file that is based on the input files it reads.
1093 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1095 # this option is superseded by the HAVE_DOT option below. This is only a
1103 # or is not a class.
1108 # available from the path. This tool is part of Graphviz, a graph visualization
1115 # will generate a graph for each documented class showing the direct and
1122 # will generate a graph for each documented class showing the direct and
1129 # will generate a graph for groups, showing the direct groups dependencies
1134 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1145 # tags are set to YES then doxygen will generate a graph for each documented
1152 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1159 # generate a call dependency graph for every global function or class method.
1160 # Note that enabling this option will significantly increase the time of a run.
1167 # will graphical hierarchy of all classes instead of a textual one.
1172 # then doxygen will show the dependencies a directory has on other directories
1173 # in a graphical way. The dependency relations are determined by the #include
1196 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1204 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1213 # from the root by following a path via at most 3 edges will be shown. Nodes
1216 # code bases. Also note that a graph may be further truncated if the graph's
1223 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1224 # background. This is disabled by default, which results in a white background.
1226 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1239 # generate a legend page explaining the meaning of the various boxes and
1254 # The SEARCHENGINE tag specifies whether or not a search engine should be