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
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
88 # "represents" "a" "an" "the"
93 # Doxygen will generate a detailed section even if there is only a brief
99 # inherited members of a class in the documentation of that class as if those
112 # can be used to strip a user-defined part of the path. Stripping is
120 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
121 # the path mentioned in the documentation of a class, which tells
122 # the reader which header file to include in order to use a class.
136 # will interpret the first line (until the first dot) of a JavaDoc-style
139 # explicit @brief command for a brief description.
144 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
145 # comments) as a brief description. This used to be the default behaviour.
146 # The new default is to treat a multi-line C++ comment block as a detailed
167 # all members of a group must be documented explicitly.
172 # a new page for each member. If set to NO, the documentation of a member will
177 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
182 # This tag can be used to specify a number of aliases that acts
186 # will result in a user-defined paragraph with heading "Side Effects:".
206 # the same type (for instance a group of public functions) to be put as a
224 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
229 # If the EXTRACT_STATIC tag is set to YES all static members of a file
270 # documentation blocks found inside the body of a function.
277 # that is typed after a \internal command is included. If the tag is set
298 # will put a list of the files that are included by a file in the documentation
303 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
362 # the initial value of a variable or define consists of for it to appear in
364 # here it will be hidden. Use a value of 0 to hide initializers completely.
383 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
416 # parameters in a documented function, or documenting parameters that
438 # The WARN_LOGFILE tag can be used to specify a file to which warning
471 # excluded from the INPUT source files. This way you can easily exclude a
472 # subdirectory from a directory tree whose root is specified with the INPUT tag.
477 # directories that are symbolic links (a Unix filesystem feature) are excluded
516 # The INPUT_FILTER tag can be used to specify a program that doxygen should
526 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
528 # filter if there is a match. The filters are a list of the form:
545 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
584 # will generate a verbatim copy of the header file for each class for
595 # contains a lot of classes, structs, unions or interfaces.
601 # in which this list will be split (can be a number in the range [1..20])
605 # In case all classes in a project start with a common prefix, all
622 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
633 # The HTML_HEADER tag can be used to specify a personal HTML header for
634 # each generated HTML page. If it is left blank doxygen will generate a
639 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
640 # each generated HTML page. If it is left blank doxygen will generate a
645 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
648 # will generate a default style sheet. Note that doxygen will try to copy
656 # NO a bullet list will be used.
662 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
669 # can add a path in front of the file if the result should not be
682 # controls if a separate .chi index file is generated (YES) or that
688 # controls whether a binary table of contents is generated (YES) or a
709 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
710 # generated containing a tree-like index structure (just like the one that
711 # is generated for HTML Help). For this to work a browser that supports
734 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
767 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
769 # the first chapter. If it is left blank doxygen will generate a
777 # This makes the output suitable for online browsing using a pdf viewer.
782 # plain latex in the generated Makefile. Set this option to YES to get a
811 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
832 # config file, i.e. a series of assignments. You only have to provide
852 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
881 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
887 # which can be used by a validating XML parser to check the
893 # which can be used by a validating XML parser to check the
922 # generate a Perl module file that captures the structure of
936 # nicely formatted so it can be parsed by a human reader. This is useful
962 # compilation will be performed. Macro expansion can be done in a controlled
974 # in the INCLUDE_PATH (see below) will be search if a #include is found.
993 # gcc). The argument of the tag is a list of macros of the form: name
995 # omitted =1 is assumed. To prevent a macro definition from being
1002 # this tag can be used to specify a list of macro names that should be expanded.
1004 # Use the PREDEFINED tag if you want to use a different macro definition.
1010 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1022 # can be added for each tagfile. The format of a tag file without
1028 # URLs. If a location is present for each tag, the installdox tool
1030 # Note that each tag file must have a unique name
1032 # If a tag file is not located in the directory in which doxygen
1037 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1038 # a tag file that is based on the input files it reads.
1064 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1066 # this option is superseded by the HAVE_DOT option below. This is only a
1074 # or is not a class.
1079 # available from the path. This tool is part of Graphviz, a graph visualization
1086 # will generate a graph for each documented class showing the direct and
1093 # will generate a graph for each documented class showing the direct and
1100 # will generate a graph for groups, showing the direct groups dependencies
1105 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1116 # tags are set to YES then doxygen will generate a graph for each documented
1123 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1130 # generate a call dependency graph for every global function or class method.
1131 # Note that enabling this option will significantly increase the time of a run.
1138 # will graphical hierarchy of all classes instead of a textual one.
1143 # then doxygen will show the dependencies a directory has on other directories
1144 # in a graphical way. The dependency relations are determined by the #include
1167 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1175 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1184 # from the root by following a path via at most 3 edges will be shown. Nodes
1187 # code bases. Also note that a graph may be further truncated if the graph's
1194 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1195 # background. This is disabled by default, which results in a white background.
1197 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1210 # generate a legend page explaining the meaning of the various boxes and
1225 # The SEARCHENGINE tag specifies whether or not a search engine should be