| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Wrong place in comment scanner of end summary tag
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having:
```
/// \file
/// The namespace docu
namespace Demo
{
/// <summary>
/// The base class
/// </summary>
public class Base
{
/// <summary>
/// The foo function
/// </summary>
/// <remarks>
/// <param name="value">The foo parameter</param>
/// <returns>foo Something</returns>
/// </remarks>
public virtual int foo(int value);
}
}
```
and we run this with `doxygen -d commentscan` we see that the `</summary>` is in the detailed part and not in the brief part:
```
CommentScanner: D:/speeltuin/issue_7356/bug_csharp_summary/Class1.cs:6
input=[
<summary>
The base class
</summary>
]
-----------
CommentScanner: D:/speeltuin/issue_7356/bug_csharp_summary/Class1.cs:6
output=[
brief=[line=6
<summary>
The base class
]
docs=[line=6
</summary> ]
inbody=[line=-1
]
]
```
this happened between the versions 1.8.14(OK) and 1.8.15(wrong), most likely through an improvement in case there are multiple brief section.
In case `</summary>` we should be already in the brief section so no need to switch again as the second switch would have no effect and we would land in the details.
|
| |\ \
| | |
| | | |
issue #8362 Text of image repeated 4 times
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have in markdown image definition like:
```
```
This would result, besides the image in the text:
```
Image 1""Image 1""Image 1""Image 1""
```
due to the fact that besides the HTML image also the image code for other output formats (latex, rtf, docbook) was written and the double quote was not escaped properly.
|
| |\ \ \
| | | |
| | | | |
Extended doxygen version information
|
| | |/ /
| | |
| | |
| | | |
Create possibility for extended version information with included extra possibilities (clang / sqlite3 / ...) by means of the options `-V` / `--Version` / `--VERSION`.
|
| |\ \ \
| | | |
| | | | |
add config option WARN_IF_INCOMPLETE_DOC
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
make docs failed because of outdated ref (I renamed the parameter to
WARN_IF_INCOMPLETE_DOC to support generalizing the idea of "do not warn
on incomplete doc of x".
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a new warning class, "INCOMPLETE_DOC", and warning option
"WARN_IF_INCOMPLETE_DOC", to control whether you get a warning
for only documenting some of your function parameters.
All users who want to retain the current behavior set
WARN_IF_INCOMPLETE_DOC to the value of WARN_IF_DOC_ERROR.
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
For easier comparison of the original source with a doxygen preprocessed source the line numbers can be a bit of an obstacle.
To remove the line numbers in the preprocessor output the option `NoLineno` has been added.
(In case `Preprocessor` is not invoked, `NoLineno` has no effect).
|
| |\ \ \
| | | |
| | | | |
Fix no callgraph being generated if having multiple 'using namespace' directives.
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | | |
- found when running tests with TEST_FLAGS="--pdf"
- due to an empty list when using FULL_PATH_NAMES = YES
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| | |
including the @ingroup marked classes in the generated documentation.
|
| | | |
|
| | |
| |
| |
| | |
dotgroupcollaboration.cpp
|
| |\ \
| | |
| | | |
issue #8160 Use ^^ instead of \n in ALIASES documentation
|
| | | |
| | |
| | |
| | |
| | | |
document
Fix the document.
|
| |\ \ \
| | | |
| | | | |
issue #8357 XML output does not include cross-references in code-fragments
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
In case of explicit code samples the language was not specified for the code and the code was parsed verbatim.
Same was valid for code in the Docbook output.
The LaTeX version has been taken as reference for the implementation.
|
| |/ /
| |
| |
| |
| | |
When searching whether the extension is already in the list of mapped extensions the input extension is used but when inserting the eventually corrected extension (extName) is used.
In all cases the inserted extension contains a dot (`.`) , but for the input extension this is not necessarily the case. This can cause problems when searching for an extension as the search will always search wit a dot and thus find the first (is old) value.
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
Spelling correction
|
| | | | |
| | | |
| | | |
| | | | |
Some spelling corrections.
|
| |/ / / |
|
| | | |
| | |
| | |
| | | |
- prepend flag was interpreted wrongly
|
| | | |
| | |
| | |
| | |
| | | |
- Found while running doxygen on the gmic project
- Cause: vector.back() was called on an empty vector
|
| |/ /
| |
| |
| |
| | |
- Found when running doxygen on the reportlab project
- Cause: top() was called on an empty stack.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
