| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
<path_to_html_output>/graph_legend.png onto itself!
In version 1.8.14 the message "Source and Destination are the same!" was given, this message could not be suppressed as can be done with normal warnings, this was corrected in 1.8.15 but backfires in case `WARN_AS_ERROR` is set. The problem only occurs when the output directory is searched for images.
Removed the message as it does not contain real information.
|
|/ / / / |
|
|\ \ \ \
| | |_|/
| |/| | |
|
| |\ \ \
| | | | |
| | | | | |
Bug 766508 - missing comments of overridden methods
|
| | | | |
| | | | |
| | | | |
| | | | | |
Analogous to python also for PHP and Java all functions are by default virtual (for python fix see problem #6566 and fix #6570)
|
| |\ \ \ \
| | | | | |
| | | | | | |
Double id for tooltips in XHTML possible.
|
| | | |_|/
| | |/| |
| | | | |
| | | | | |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Bug 626582 - Function overloads are not actually sorted in member function list
|
| | |/ /
| |/| |
| | | |
| | | | |
List was only sorted on member names, now also subsequently sorted on arguments.
|
|\ \ \ \
| | | | |
| | | | | |
Bug 141919 - Wrong param and exception style in RTF output
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some small improvements in the different formats based on the problems signaled with the issue
- doxygen.css make exceptions in line with other tables (i.e. the appearance of the name of the exception)
- doxygen.sty, rtfdocvisitor.cpp between items in e.g. Precondition, Postcondition, Note place a paragraph distance (like in main text)
- docbookvisitor.cpp handle title of Rcs and User sections correctly
.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
issue #6828 Physical newlines (^^) in ALIASES configuration tags not working with sections, subsections, subsubsections and paragraphs
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
with sections, subsections, subsubsections and paragraphs
Previous changes corrected use of _linebr, missed one so this was not handled properly.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Issue #6818 Certain regex pattern in class constant causes PHP class to be ignored
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ignored
In case of Cpp we also have to consider the case of strings that can contain the `[[...]]` part.
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ignored
Only ally the rule `<*>"[["` for Cpp
See also fix d8001efd89146e04d92f5ea41ab27a7de09b6c53 i.e. Problem parsing c++ gnu::visibility (Origin: bugzilla #787952) #6259
|
|/ / / /
| | | |
| | | |
| | | | |
with static libclang.
|
| | | |
| | | |
| | | |
| | | | |
operators in 1.8.15
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Portuguse translators updated to Doxygen 1.8.16.
|
| | | |_|/
| | |/| | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
Warning for documented return of void type function
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case a void type function is documented it is not allowed to used a `\return` or `\retval` command. The test was present but not correct
- test on `g_hasReturnCommand ` which signals whether of not `\ret...` is used instead of `g_memberDef->hasDocumentedReturnType()`
- removed test on emty return type (empty return type is assumed to be non void, see e.g. C, Fortran).
- order of the tests is important
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
issue #6812 Empty lines are lost when copy-pasting from code section.
|
| | |/ /
| |/| |
| | | |
| | | | |
In case of an empty line insert an space so the line will be shown with copy & paste (including the space!).
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
|/ / /
| | |
| | |
| | |
| | | |
Problem occurs when a line with just a `*` is followed by another line with an `# and some comment. The test on newline has been removed.
Problem is most likely a consequence of Bug #5288 - Asterisks in comment wrongly displayed for @code, i.e. 23f337e64b95d3fa08f32980c866669b190c872f
|
| | | |
|
|\ \ \ |
|
| |\ \ \
| | | | |
| | | | | |
Inline VHDL code
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Based on the example of #6805
- First line of inline documentation didn't have a line number
- The line numbers in inline documentation were off by one
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
|
| |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6800
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
In case of a completely empty line with 2 spaces at the end don't consider this as a 2 space terminated line.
Regression of #6448
|
|\ \ \ \ |
|
| | | | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
issue #6796 Bad link to section, subsection if pointing at item past suspicious text
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
suspicious text
To escape `\` and `@` not only `\\` and `@@` should be possible but also `\@` and `@\`
|
|/ / / |
|
|\ \ \ |
|
| |\ \ \
| | |/ /
| |/| | |
issue #6791 TOC not generated when using a particular Markdown headerstyle
|
| | | |
| | | |
| | | |
| | | | |
Update test
|
| |/ /
| | |
| | |
| | |
| | | |
The default for the `TOC_INCLUDE_HEADERINGS` was set to 0, for compatibility this should be 5.
(Problem was observed in the doxygen documentation, chapter markdown, where the TOC was missing; alternatively in the Doxyfile the `TOC_INCLUDE_HEADERINGS` could be set to `5`,. The solution chosen is more consistent with the old situation).
|
| |\ \
| | |/
| |/| |
issue #6679 Multiple use of section label warning for Setex-stype headers in markdown
|
| |/
| |
| |
| |
| |
| |
| |
| | |
markdown
Due to the move of the markdown code to another place the adding of the section info of section, subsection etc. would be attempted to add twice (first in markdown and later on again when translating the resulting '`section`, `\subsection` commands. The adding should only take place when handling the (replaced) commands.
Removing the test in `addSection` won't work as in that case using twice a sectioning command with the same label would not be signaled anymore.
|