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
17 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
30 # If a relative path is entered, it will be relative to the location
38 # Enabling this option can be useful when feeding doxygen a huge amount of source
59 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
61 # whereas setting the tag to NO uses a Unix-style encoding (the default for
74 # the brief description of a member or function before the detailed description.
80 # This tag implements a quasi-intelligent brief description abbreviator
87 # "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
92 # Doxygen will generate a detailed section even if there is only a brief
98 # members of a class in the documentation of that class as if those members were
111 # can be used to strip a user-defined part of the path. Stripping is
119 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120 # the path mentioned in the documentation of a class, which tells
121 # the reader which header file to include in order to use a class.
135 # will interpret the first line (until the first dot) of a JavaDoc-style
138 # explicit @brief command for a brief description.
143 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
144 # comments) as a brief description. This used to be the default behaviour.
145 # The new default is to treat a multi-line C++ comment block as a detailed
166 # all members of a group must be documented explicitly.
170 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
175 # This tag can be used to specify a number of aliases that acts
179 # will result in a user-defined paragraph with heading "Side Effects:".
199 # the same type (for instance a group of public functions) to be put as a
217 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
222 # If the EXTRACT_STATIC tag is set to YES all static members of a file
263 # documentation blocks found inside the body of a function.
270 # that is typed after a \internal command is included. If the tag is set
291 # will put a list of the files that are included by a file in the documentation
296 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
355 # the initial value of a variable or define consists of for it to appear in
357 # here it will be hidden. Use a value of 0 to hide initializers completely.
393 # parameters in a documented function, or documenting parameters that
405 # The WARN_LOGFILE tag can be used to specify a file to which warning
438 # excluded from the INPUT source files. This way you can easily exclude a
439 # subdirectory from a directory tree whose root is specified with the INPUT tag.
444 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
480 # The INPUT_FILTER tag can be used to specify a program that doxygen should
490 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
492 # filter if there is a match. The filters are a list of the form:
509 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
540 # will generate a verbatim copy of the header file for each class for
551 # contains a lot of classes, structs, unions or interfaces.
557 # in which this list will be split (can be a number in the range [1..20])
561 # In case all classes in a project start with a common prefix, all
578 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
589 # The HTML_HEADER tag can be used to specify a personal HTML header for
590 # each generated HTML page. If it is left blank doxygen will generate a
595 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
596 # each generated HTML page. If it is left blank doxygen will generate a
601 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
604 # will generate a default style sheet. Note that doxygen will try to copy
612 # NO a bullet list will be used.
618 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
625 # can add a path in front of the file if the result should not be
638 # controls if a separate .chi index file is generated (YES) or that
644 # controls whether a binary table of contents is generated (YES) or a
665 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
666 # generated containing a tree-like index structure (just like the one that
667 # is generated for HTML Help). For this to work a browser that supports
690 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
723 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
725 # the first chapter. If it is left blank doxygen will generate a
733 # This makes the output suitable for online browsing using a pdf viewer.
738 # plain latex in the generated Makefile. Set this option to YES to get a
767 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
788 # config file, i.e. a series of assignments. You only have to provide
808 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
837 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
843 # which can be used by a validating XML parser to check the
849 # which can be used by a validating XML parser to check the
878 # generate a Perl module file that captures the structure of
892 # nicely formatted so it can be parsed by a human reader. This is useful
918 # compilation will be performed. Macro expansion can be done in a controlled
930 # in the INCLUDE_PATH (see below) will be search if a #include is found.
949 # gcc). The argument of the tag is a list of macros of the form: name
956 # this tag can be used to specify a list of macro names that should be expanded.
958 # Use the PREDEFINED tag if you want to use a different macro definition.
964 # on a line, have an all uppercase name, and do not end with a semicolon. Such
976 # can be added for each tagfile. The format of a tag file without
982 # URLs. If a location is present for each tag, the installdox tool
984 # Note that each tag file must have a unique name
986 # If a tag file is not located in the directory in which doxygen
991 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
992 # a tag file that is based on the input files it reads.
1018 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
1020 # option is superseded by the HAVE_DOT option below. This is only a fallback. It is
1027 # or is not a class.
1032 # available from the path. This tool is part of Graphviz, a graph visualization
1039 # will generate a graph for each documented class showing the direct and
1046 # will generate a graph for each documented class showing the direct and
1053 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1064 # tags are set to YES then doxygen will generate a graph for each documented
1071 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1078 # generate a call dependency graph for every global function or class method.
1079 # Note that enabling this option will significantly increase the time of a run.
1086 # will graphical hierarchy of all classes instead of a textual one.
1108 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1116 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1125 # from the root by following a path via at most 3 edges will be shown. Nodes that
1128 # note that a graph may be further truncated if the graph's image dimensions are
1135 # generate a legend page explaining the meaning of the various boxes and
1150 # The SEARCHENGINE tag specifies whether or not a search engine should be