Lines Matching refs:line
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
184 # first line (until the first dot) of a Javadoc-style comment as the brief
192 # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
203 # line (until the first dot) of a Qt-style comment as the brief description. If
211 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
213 # to treat a multi-line C++ comment block as a detailed description. Set this
842 # can produce. The string should contain the $file, $line, and $text tags, which
843 # will be replaced by the file and line number from which the warning originated
847 # The default value is: $file:$line: $text.
849 WARN_FORMAT = "$file:$line: $text"
1107 # tools must be available from the command line (i.e. in the search path).
1144 # line options that you would normally use when invoking the compiler. Note that
1578 # doxygen will group on one line in the generated HTML documentation.
2263 # remove all references to function-like macros that are alone on a line, have
2605 # files in one run (i.e. multiple -o and -T options on the command line). This