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
245 # documentation. This will only work if the methods are indeed getting or
251 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
252 # tag is set to YES, then doxygen will reuse the documentation of the first
268 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
297 # documentation are documented, even if no documentation was available.
304 # will be included in the documentation.
309 # will be included in the documentation.
314 # defined locally in source files will be included in the documentation.
321 # the interface are included in the documentation.
327 # extracted and appear in the documentation as a namespace called
337 # various overviews, but no documentation section is generated.
352 # documentation.
357 # documentation blocks found inside the body of a function.
359 # function's detailed documentation block.
363 # The INTERNAL_DOCS tag determines if documentation
365 # to NO (the default) then the documentation will be excluded.
366 # Set it to YES to include the internal documentation.
380 # documentation. If set to YES the scope will be hidden.
385 # will put a list of the files that are included by a file in the documentation
391 # will list include files with double quotes in the documentation
397 # is inserted in the documentation for inline members.
402 # will sort the (detailed) documentation of file and class members
409 # brief documentation of file, namespace and class members alphabetically
416 # will sort the (brief and detailed) documentation of class members so that
443 # commands in the documentation.
449 # commands in the documentation.
455 # commands in the documentation.
461 # \deprecated commands in the documentation.
466 # documentation sections, marked by \if sectionname ... \endif.
472 # the documentation. If the initializer consists of more lines than specified
475 # documentation can be controlled using \showinitializer or \hideinitializer
476 # command in the documentation regardless of this setting.
481 # at the bottom of the documentation of classes and structs. If set to YES the
482 # list will mention the files that were used to generate the documentation.
488 # in the documentation. The default is NO.
546 # potential errors in the documentation, such as not documenting some
553 # functions that are documented, but have no documentation for their parameters
555 # wrong or incomplete parameter documentation, but not about the absence of
556 # documentation.
660 # directories that contain image that are included in the documentation (see
705 # of functions and classes directly in the documentation.
731 # Otherwise they will link to the documentation.
852 # documentation will contain sections that can be hidden and shown after the
862 # To create a documentation set, doxygen will generate a Makefile in the
873 # feed. A documentation feed provides an umbrella under which multiple
874 # documentation sets from a single provider (such as a company or product suite)
880 # should uniquely identify the documentation set bundle. This should be a
887 # the documentation publisher. This should be a reverse domain-name style
888 # string, e.g. com.mycompany.MyDocSet.documentation.
892 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
899 # of the generated HTML documentation.
936 # to the contents of the HTML help documentation and to the tree view.
943 # Qt Compressed Help (.qch) of the generated HTML documentation.
1017 # that doxygen will group on one line in the generated HTML documentation.
1048 # as images in the HTML documentation. The default is 10. Note that
1145 # higher quality PDF documentation.
1245 # the code including all documentation.
1281 # documentation. Note that this feature is still experimental
1292 # the code including all documentation. Note that this
1392 # Optionally an initial location of the external documentation
1448 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1582 # contain dot files that are included in the documentation (see the