Lines Matching refs:a

4 # doxygen (www.doxygen.org) for a project
6 # All text after a hash (#) is considered a comment and will be ignored
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
38 # If a relative path is entered, it will be relative to the location
46 # Enabling this option can be useful when feeding doxygen a huge amount of
72 # the brief description of a member or function before the detailed description.
78 # This tag implements a quasi-intelligent brief description abbreviator
86 # "represents" "a" "an" "the"
91 # Doxygen will generate a detailed section even if there is only a brief
97 # inherited members of a class in the documentation of that class as if those
110 # can be used to strip a user-defined part of the path. Stripping is
118 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
119 # the path mentioned in the documentation of a class, which tells
120 # the reader which header file to include in order to use a class.
134 # will interpret the first line (until the first dot) of a JavaDoc-style
137 # explicit @brief command for a brief description.
142 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
143 # comments) as a brief description. This used to be the default behaviour.
144 # The new default is to treat a multi-line C++ comment block as a detailed
163 # a new page for each member. If set to NO, the documentation of a member will
168 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
173 # This tag can be used to specify a number of aliases that acts
177 # will result in a user-defined paragraph with heading "Side Effects:".
197 # include (a tag file for) the STL sources as input, then you should
213 # all members of a group must be documented explicitly.
218 # the same type (for instance a group of public functions) to be put as a
236 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
241 # If the EXTRACT_STATIC tag is set to YES all static members of a file
282 # documentation blocks found inside the body of a function.
289 # that is typed after a \internal command is included. If the tag is set
310 # will put a list of the files that are included by a file in the documentation
315 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
374 # the initial value of a variable or define consists of for it to appear in
376 # here it will be hidden. Use a value of 0 to hide initializers completely.
395 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
428 # parameters in a documented function, or documenting parameters that
450 # The WARN_LOGFILE tag can be used to specify a file to which warning
491 # excluded from the INPUT source files. This way you can easily exclude a
492 # subdirectory from a directory tree whose root is specified with the INPUT tag.
497 # directories that are symbolic links (a Unix filesystem feature) are excluded
512 # The symbol name can be a fully qualified name, a word, or if the wildcard * is used,
513 # a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test
543 # The INPUT_FILTER tag can be used to specify a program that doxygen should
553 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
555 # filter if there is a match.  The filters are a list of the form:
572 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
618 # will generate a verbatim copy of the header file for each class for
629 # contains a lot of classes, structs, unions or interfaces.
635 # in which this list will be split (can be a number in the range [1..20])
639 # In case all classes in a project start with a common prefix, all
656 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
667 # The HTML_HEADER tag can be used to specify a personal HTML header for
668 # each generated HTML page. If it is left blank doxygen will generate a
673 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
674 # each generated HTML page. If it is left blank doxygen will generate a
679 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
682 # will generate a default style sheet. Note that doxygen will try to copy
690 # NO a bullet list will be used.
696 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
703 # can add a path in front of the file if the result should not be
716 # controls if a separate .chi index file is generated (YES) or that
722 # controls whether a binary table of contents is generated (YES) or a
743 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
744 # generated containing a tree-like index structure (just like the one that
745 # is generated for HTML Help). For this to work a browser that supports
768 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
801 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
803 # the first chapter. If it is left blank doxygen will generate a
811 # This makes the output suitable for online browsing using a pdf viewer.
816 # plain latex in the generated Makefile. Set this option to YES to get a
845 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
866 # config file, i.e. a series of assignments. You only have to provide
886 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
915 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
921 # which can be used by a validating XML parser to check the
927 # which can be used by a validating XML parser to check the
956 # generate a Perl module file that captures the structure of
970 # nicely formatted so it can be parsed by a human reader.  This is useful
996 # compilation will be performed. Macro expansion can be done in a controlled
1008 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1027 # gcc). The argument of the tag is a list of macros of the form: name
1029 # omitted =1 is assumed. To prevent a macro definition from being
1036 # this tag can be used to specify a list of macro names that should be expanded.
1038 # Use the PREDEFINED tag if you want to use a different macro definition.
1044 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1056 # can be added for each tagfile. The format of a tag file without
1062 # URLs. If a location is present for each tag, the installdox tool
1064 # Note that each tag file must have a unique name
1066 # If a tag file is not located in the directory in which doxygen
1071 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1072 # a tag file that is based on the input files it reads.
1098 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1100 # this option is superseded by the HAVE_DOT option below. This is only a
1116 # or is not a class.
1121 # available from the path. This tool is part of Graphviz, a graph visualization
1128 # will generate a graph for each documented class showing the direct and
1135 # will generate a graph for each documented class showing the direct and
1142 # will generate a graph for groups, showing the direct groups dependencies
1147 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1158 # tags are set to YES then doxygen will generate a graph for each documented
1165 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1172 # generate a call dependency graph for every global function or class method.
1173 # Note that enabling this option will significantly increase the time of a run.
1180 # generate a caller dependency graph for every global function or class method.
1181 # Note that enabling this option will significantly increase the time of a run.
1188 # will graphical hierarchy of all classes instead of a textual one.
1193 # then doxygen will show the dependencies a directory has on other directories
1194 # in a graphical way. The dependency relations are determined by the #include
1217 # nodes that will be shown in the graph. If the number of nodes in a graph
1219 # visualized by representing a node as a red box. Note that doxygen will always
1224 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1225 # background. This is disabled by default, which results in a white background.
1227 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1240 # generate a legend page explaining the meaning of the various boxes and
1255 # The SEARCHENGINE tag specifies whether or not a search engine should be