Lines Matching refs:code
226 # uses this value to replace tabs by spaces in code fragments.
284 # Fortran. In the later case the parser tries to guess whether the code is fixed
285 # or free formatted code, this is the default for Fortran type files), VHDL. For
407 # useful for C code in case the coding convention dictates that all compound
416 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
466 # This flag is only useful for Objective-C code. If set to YES, local methods,
879 # that contain example code fragments that are included (see the \include
916 # code is scanned, but not when the output code is generated. If lines are added
967 # Note: To get rid of all source code in the generated output, make sure that
980 # special comment blocks from generated source code fragments. Normal C, C++ and
1000 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1007 # source code will show a tooltip with additional information such as prototype,
1016 # If the USE_HTAGS tag is set to YES then the references to source code will
1032 # source code will now point to the output of htags.
1523 # of code that will be used on startup of the MathJax code. See the MathJax site
1760 # code with syntax highlighting in the LaTeX output.
1841 # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1900 # captures the structure of the code including all documentation.
1955 # structure of the code including all documentation. Note that this feature is
1966 # file that captures the structure of the code including all documentation.
1974 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2010 # in the source code. If set to NO, only conditional compilation will be
2065 # definition found in the source code.
2083 # are typically used for boiler-plate code, and will confuse the parser if not
2419 # or 2 may greatly reduce the computation time needed for large code bases. Also