Lines Matching full:documentation
3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
98 # inherited members of a class in the documentation of that class as if those
120 # the path mentioned in the documentation of a class, which tells
159 # member inherits the documentation from any documented member that it
165 # a new page for each member. If set to NO, the documentation of a member will
176 # as commands in the documentation. An alias has the form "name=value".
178 # put the command \sideeffect (or @sideeffect) in the documentation, which
244 # documentation. This will only work if the methods are indeed getting or
250 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
251 # tag is set to YES, then doxygen will reuse the documentation of the first
267 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
296 # documentation are documented, even if no documentation was available.
303 # will be included in the documentation.
308 # will be included in the documentation.
313 # defined locally in source files will be included in the documentation.
320 # the interface are included in the documentation.
326 # extracted and appear in the documentation as a namespace called
336 # various overviews, but no documentation section is generated.
351 # documentation.
356 # documentation blocks found inside the body of a function.
358 # function's detailed documentation block.
362 # The INTERNAL_DOCS tag determines if documentation
364 # to NO (the default) then the documentation will be excluded.
365 # Set it to YES to include the internal documentation.
379 # documentation. If set to YES the scope will be hidden.
384 # will put a list of the files that are included by a file in the documentation
390 # will list include files with double quotes in the documentation
396 # is inserted in the documentation for inline members.
401 # will sort the (detailed) documentation of file and class members
408 # brief documentation of file, namespace and class members alphabetically
414 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
436 # commands in the documentation.
442 # commands in the documentation.
448 # commands in the documentation.
454 # \deprecated commands in the documentation.
459 # documentation sections, marked by \if sectionname ... \endif.
465 # the documentation. If the initializer consists of more lines than specified
468 # documentation can be controlled using \showinitializer or \hideinitializer
469 # command in the documentation regardless of this setting.
474 # at the bottom of the documentation of classes and structs. If set to YES the
475 # list will mention the files that were used to generate the documentation.
481 # in the documentation. The default is NO.
539 # potential errors in the documentation, such as not documenting some
546 # functions that are documented, but have no documentation for their parameters
548 # wrong or incomplete parameter documentation, but not about the absence of
549 # documentation.
651 # directories that contain image that are included in the documentation (see
696 # of functions and classes directly in the documentation.
722 # Otherwise they will link to the documentation.
818 # documentation will contain sections that can be hidden and shown after the
828 # To create a documentation set, doxygen will generate a Makefile in the
831 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
838 # feed. A documentation feed provides an umbrella under which multiple
839 # documentation sets from a single provider (such as a company or product suite)
845 # should uniquely identify the documentation set bundle. This should be a
854 # of the generated HTML documentation.
891 # to the contents of the HTML help documentation and to the tree view.
898 # HTML documentation.
967 # that doxygen will group on one line in the generated HTML documentation.
993 # as images in the HTML documentation. The default is 10. Note that
1075 # higher quality PDF documentation.
1172 # the code including all documentation.
1208 # documentation. Note that this feature is still experimental
1219 # the code including all documentation. Note that this
1319 # Optionally an initial location of the external documentation
1375 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1501 # contain dot files that are included in the documentation (see the
