| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
|
| |
| |
| |
| |
| |
| |
| |
| | |
There are 2 different situations here:
- @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp)
- @param
- the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*).
- In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
|
|\ \
| | |
| | | |
Incorrect paragraph numbers in secref list.
|
|/ /
| |
| |
| |
| |
| |
| | |
The definition of `\doxysection` etc. are using grouping around the section title, and this destroys the \label system as label names are stored locally.
(see also: https://tex.stackexchange.com/questions/502650/section-numbering-in-redefined-sections)
the `\doxysection` commands have been redefined (unfortunately partly copying values from book.cls)
|
|\ \ |
|
| | | |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doc_cont
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have a documentation block that is interrupted the following part is directly appended to it without an appropriate newline and results, in this case, in messages like:
```
aa.c:13: warning: Illegal command @verbatim as part of a title section
aa.c:15: warning: unexpected command endverbatim
bb.f:13: warning: Illegal command @verbatim as part of a title section
bb.f:15: warning: unexpected command endverbatim
```
We need a solution at 2 places due to the reset of of `OutputBrief` to `OutputDoc` in `setOutput`
The original problem results from the "The R Project for Statistical Computing" version 3.6.1 in the Fortran part.
|
|\ \ \ |
|
| | | | |
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_if_unbalanced
|
| | | |
| | | |
| | | |
| | | | |
In case in a macro substitution string the last character was a backslash this was, incorrect, not seen as a sign for a line continuation.
|
|\ \ \ \ |
|
| | | | | |
|
| |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Github does not support the `<u>` tag for underlined text, in HTML there exists the tag `<ins>`. On https://www.w3schools.com/tags/tag_ins.asp is written:
The `<ins>` tag defines a text that has been inserted into a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<ins>` element with the following default values:
```
ins {
text-decoration: underline;
}
```
analogous there exists the tag `<del>` (https://www.w3schools.com/tags/tag_del.asp):
The `<del>` tag defines text that has been deleted from a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<del>` element with the following default values:
```
del {
text-decoration: line-through;
}
```
Definitions analogue to the underline and strike through tag the implementation for the other formats has been chosen.
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
warning: Reached end of file while still inside a (nested) comment.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
see to it that the JAVA_BANNER comment is not seen as new start of comment, but is shown as verbatim comment (works for doxygen documentation, Doxyfile and doxywizard).
|
|/ / / / / / |
|
|\ \ \ \ \ \
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
warning: Member func2InGroup1() (function) of class Memgrp_Test is not documented.
|
| | | |/ / /
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
documented.
Correcting code due to the fact that `//@{` isn't seen by doxygen as block start (#7116).
Thi s problem is shown when generating the doxygen documentation.
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | |/ / / /
| |/| | | | |
issue #7151 Doxygen 1.8.15 TOC_INCLUDE_HEADINGS >0 stops html links being generated in markdown
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
generated in markdown
Don't create autotoc generated ids for pages.
(the `\ref` problem also occurred with `\subage`).
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Regression on #7122 (and #7115 / #7116).
When having multiple consecutive `\name` sections the warning "unbalanced grouping commands" appears
Analogous to the open command also the close command needs an implicit argument.
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_retval_mult
|
| | | | |
| | | | |
| | | | |
| | | | | |
Analogous to arguments when they have multiple `\param` commands this is also done when a return value is specified multiple times with the `\retval` command
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Update internal Doxyfile to current version / situation
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
issue #7113 Doxygen doesn't process markdown tables correctly
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Better to have the end tag start at a new line so it cannot be added to a command that runs till the end of the line
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Removed superfluous character
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
issue #7109 Doxyapp can't use "[source_file | source_dir]" parameter
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
- setting RECURSIVE (required for directories)
- making check / adjust consistent with doxyparse
|
| | |/ / / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- initialization has to be done in an earlier stage (and only once)
- not only the INPUT tag was involved, none of the tags were set.
|
|\ \ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ \
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_685714
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
documented
- removed memory leak on variable root
- return values of generateDoc and parseText are nowhere used, replaced bool function with void function.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
documented
The "validating" routines should always be called.
They were missed out in case of:
- only XML format there should be warnings as well (XML has its own write routines)
- no formats there should be warnings as well
|
|\ \ \ \ \ \ \ \ \ |
|