Lines Matching refs: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
235 # documentation. This will only work if the methods are indeed getting or
241 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
242 # tag is set to YES, then doxygen will reuse the documentation of the first
258 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
287 # documentation are documented, even if no documentation was available.
294 # will be included in the documentation.
299 # will be included in the documentation.
304 # defined locally in source files will be included in the documentation.
311 # the interface are included in the documentation.
317 # extracted and appear in the documentation as a namespace called
327 # various overviews, but no documentation section is generated.
342 # documentation.
347 # documentation blocks found inside the body of a function.
349 # function's detailed documentation block.
353 # The INTERNAL_DOCS tag determines if documentation
355 # to NO (the default) then the documentation will be excluded.
356 # Set it to YES to include the internal documentation.
370 # documentation. If set to YES the scope will be hidden.
375 # will put a list of the files that are included by a file in the documentation
381 # is inserted in the documentation for inline members.
386 # will sort the (detailed) documentation of file and class members
393 # brief documentation of file, namespace and class members alphabetically
417 # commands in the documentation.
423 # commands in the documentation.
429 # commands in the documentation.
435 # \deprecated commands in the documentation.
440 # documentation sections, marked by \if sectionname ... \endif.
446 # the documentation. If the initializer consists of more lines than specified
449 # documentation can be controlled using \showinitializer or \hideinitializer
450 # command in the documentation regardless of this setting.
455 # at the bottom of the documentation of classes and structs. If set to YES the
456 # list will mention the files that were used to generate the documentation.
462 # in the documentation. The default is NO.
519 # potential errors in the documentation, such as not documenting some
526 # functions that are documented, but have no documentation for their parameters
528 # wrong or incomplete parameter documentation, but not about the absence of
529 # documentation.
636 # directories that contain image that are included in the documentation (see
678 # of functions and classes directly in the documentation.
793 # documentation will contain sections that can be hidden and shown after the
803 # To create a documentation set, doxygen will generate a Makefile in the
813 # feed. A documentation feed provides an umbrella under which multiple
814 # documentation sets from a single provider (such as a company or product suite)
820 # should uniquely identify the documentation set bundle. This should be a
829 # of the generated HTML documentation.
866 # to the contents of the HTML help documentation and to the tree view.
873 # HTML documentation.
909 # that doxygen will group on one line in the generated HTML documentation.
937 # as images in the HTML documentation. The default is 10. Note that
1003 # higher quality PDF documentation.
1096 # the code including all documentation.
1132 # documentation. Note that this feature is still experimental
1143 # the code including all documentation. Note that this
1248 # Optionally an initial location of the external documentation
1302 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1428 # contain dot files that are included in the documentation (see the