| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
The RTF output was lacking the possibility to have formulas in it (were written as text). This patch generates the images analogous to the HTML, non MATHJAX, version and includes them in the output.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Markdown processing was done after the normal tag processing and splitting the comment in brief, doc, inline. This resulted in that sectioning parts (i.e. e.g. ==== conversion to <h1> ) remained in the brief description whilst similar constructs with HTML commands landed in the doc (details) description. By performing the markdown on the entire comment block this problem has been overcome.
commentscan.l
- change moment of calling markdown processing
- skip start spaces and subsequent empty lines in markdown processed code
- small debug correction
markdown.cpp
- don't convert the dashes in <!-- and --> (HTML type comment)
- small debug correction
054 test
- update of example for compatibility and adding part about none code result.
doxygen.cpp
- small textual comment correction
|
|
|
|
| |
template
|
|\
| |
| | |
Physical newlines in ALIASES configuration tags.
|
| |
| |
| |
| |
| |
| | |
Some commands read input till the end of the physical line. In case these commands are used in an alias the rest of the line is lost / gives not the required results.
This patch creates the possibility to have physical newlines in ALIASES.
See also: https://stackoverflow.com/questions/46050789/doxygen-alias-with-multiple-commands
|
| |
| |
| |
| |
| | |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
|/
|
|
| |
not recognized by Doxygen
|
| |
|
| |
|
|
|
|
| |
is formatted incorrectly
|
| |
|
|
|
|
|
|
| |
The original problem in this bug request was that forward slashes were used in the PATH instead of backslashes.
In the command shell this does not result in problems, but when calling a program from within doxygen this leads to the problem that the executable cannot be found.
In this patch the PATH variable is, just for the process, changed in such a way that ther are back slashes instead of forward slashes (Windows only, not on Cygwin).
|
|\
| |
| | |
Doxygen fails to copy logo image to LaTex output dir
|
| |
| |
| |
| | |
Logo was only copied for HTML, now it is done for LaTeX and RTF as well.
|
| | |
|
| | |
|
| |
| |
| |
| | |
declaration
|
|/ |
|
| |
|
|
|
|
| |
improve performance
|
|
|
|
| |
documented
|
|
|
|
| |
a warning
|
|\
| |
| | |
Add WARN_AS_ERROR option to stop execution at first warning (equivalent of compilers' -Werror option)
|
| |
| |
| |
| | |
compilers' -Werror option)
|
| |
| |
| |
| |
| |
| |
| |
| | |
From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html)
B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!).
C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance.
Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
|
| | |
|
|/
|
|
|
|
|
|
| |
From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html)
B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!).
C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance.
Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
doxygen
In case the user wants to overrule by means of a HTML_EXTRA_FILIES or LATEX_EXTRA_FILES a default file from doxygen (e.g. a logo or arrowdown) this is not directly possible as the files are again overwritten by doxygen.
Placing the copy commands at the end and in this list the generateTreeViewImages before the the user files a user can overrule default doxygen files
|
| |
|
|\
| |
| | |
specify that doxygen searches files in INPUT tag
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
|/ |
|
| |
|
|\
| |
| | |
Fix missing brief documentation for overload and specialization function...
|
| |
| |
| |
| |
| |
| |
| |
| | |
Brief documentation entries were not added for template specializations or
overload definitions. Adding brief documentation to those function definations
fixes a corner case bug #406027
Bug 406027 - Templated class member specialization cannot be documented
|
|\ \
| |/ |
|
| |
| |
| |
| | |
this may help debugging the source of the error
|
| |
| |
| |
| |
| | |
Based on the report in the doxygen forum (http://doxygen.10944.n7.nabble.com/WARNING-Found-more-than-one-mainpage-comment-block-td7092.html) about the hard to find multiple occurrences of a mainpage definition.
This patch also outputs the name (and approximate line) of the first found mainpage.
|
|/
|
|
| |
classes.
|
| |
|
|\
| |
| | |
Consistency in handling HTML and LaTeX in respect to header and footer
|
| |
| |
| |
| |
| | |
There was a discrepancy in the handling of the header and footer files between HTML and LaTeX.
Also the wrong error / warning routine was called and the config_err and config_warn have been made more consistent with the messages(.cpp)
|