Lines Matching refs:documentation

3 # This file describes the settings to be used by the documentation system
23 # This could be handy for archiving the generated documentation or 
29 # base path where the generated documentation will be put. 
36 # documentation generated by doxygen is written. Doxygen will use this 
47 # documentation are documented, even if no documentation was available. 
54 # will be included in the documentation.
59 # will be included in the documentation.
64 # defined locally in source files will be included in the documentation. 
72 # various overviews, but no documentation section is generated. 
87 # documentation.
92 # documentation blocks found inside the body of a function. 
94 # function's detailed documentation block.
100 # the file and class documentation (similar to JavaDoc). 
119 # members of a class in the documentation of that class as if those members were 
138 # The INTERNAL_DOCS tag determines if documentation 
140 # to NO (the default) then the documentation will be excluded. 
141 # Set it to YES to include the internal documentation.
161 # documentation. If set to YES the scope will be hidden.
172 # will put list of the files that are included by a file in the documentation 
196 # documentation.
201 # member inherits the documentation from any documented member that it 
207 # is inserted in the documentation for inline members.
212 # will sort the (detailed) documentation of file and class members 
218 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
219 # tag is set to YES, then doxygen will reuse the documentation of the first 
232 # commands in the documentation.
238 # commands in the documentation.
244 # commands in the documentation.
250 # \deprecated commands in the documentation.
255 # as commands in the documentation. An alias has the form "name=value". 
257 # put the command \sideeffect (or @sideeffect) in the documentation, which 
264 # documentation sections, marked by \if sectionname ... \endif.
270 # the documentation. If the initializer consists of more lines than specified 
273 # documentation can be controlled using \showinitializer or \hideinitializer 
274 # command in the documentation regardless of this setting.
293 # at the bottom of the documentation of classes and structs. If set to YES the 
294 # list will mention the files that were used to generate the documentation.
320 # potential errors in the documentation, such as not documenting some 
403 # directories that contain image that are included in the documentation (see 
433 # of functions and classes directly in the documentation.
527 # of the generated HTML documentation.
558 # to the contents of the Html help documentation and to the tree view.
569 # that doxygen will group on one line in the generated HTML documentation.
647 # higher quality PDF documentation.
734 # the code including all documentation. Note that this 
759 # documentation. Note that this feature is still experimental 
770 # the code including all documentation. Note that this 
966 # contain dot files that are included in the documentation (see the 
1015 # cgi binaries are located. See the documentation of your http daemon for 
1021 # documentation is located. If left blank the absolute path to the 
1022 # documentation, with file:// prepended to it, will be used.
1027 # documentation is located. If left blank the directory on the local machine 
1038 # documentation generated for other projects. This allows doxysearch to search 
1039 # the documentation for these projects as well.