| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also prepared some code for multi-threaded use, and
Removed tabs and trailing spaces for code.l
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When having a (stripped down) example like:
```
!
!!/*T
!T*/
```
we get a warning like:
```
.../ex11f.F90:4: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 2, 2)
```
even though Fortran has no nested comments, and certainly doesn't have `/*` as comment signs. So message can be ignored.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having an example like:
```
## General \PYgen0 docu
#
#
#
#
# General detail \PYgen1 text
# and more
STYLE_TEMPLATE = r'''
\makeatletter
'''
## General \PYgen2 docu
#
#
#
#
#
# General detail \PYgen3 text
# and more
STYLE_TEMPLATE1 = r'''
\makeatletter
'''
```
with
```
EXTRACT_ALL = YES
QUIET = YES
```
we get the warnings (removed doubles and sorted):
```
bb.py:1: warning: Found unknown command '\PYgen0'
bb.py:10: warning: Found unknown command '\PYgen1'
bb.py:12: warning: Found unknown command '\PYgen2'
bb.py:23: warning: Found unknown command '\PYgen3'
```
we see here (especially with `PYgen3` a wrong line number.
After fixing the line count in `pyscanner.l` there was for the second block an offset of 1. This was caused by `commentscan.l` introduced with #7960 after correcting this this offset was also gone.
Revisiting the original example of #7960 showed that here here was also an offset of 1 (probably due to a misinterpretation of where the `<tr>` warning should be mentioned), here it is now also correct..
(The original mismatch was shown of Fossies for the Pygments package)
|
| |
|
|
|
| |
* Fix too aggressive giphenation of abbr. words.
* Remove unwanted change at line 2266
|
| |\
| |
| | |
Incorrect duplicate code for Fortran fixed/free recognition
|
| | |
| |
| |
| | |
There were 2 routines to recognize whether Fortran code was Fixed of Free format code, though the version in `commentcnv.l` didn't take the settings of `EXTENSION_MAPPING` into account which might lead to incorrect recognition of the format, this has been corrected.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
* Proposed fix for issue #7898 - Internal search engine produce ".html" pages instead of using HTML_FILE_EXTENSION
* Applied albert-github suggestions to proposed fix for issue #7898
|
| |/ / |
|
| | |
| |
| |
| | |
default
|
| |\ \
| | |
| | |
| | | |
into tolnaisz-arg_name_as_comment
|
| | | |
| | |
| | |
| | | |
EXTRACT_ANON_ARGUMENTS.
|
| |\ \ \
| | | |
| | | | |
Warning about end of list in brief description after alias `^^` replacement
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the alias:
```
ALIASES += "sbl_add_package_main_class{2}=\brief \1 ^^ \2"
```
and the comment:
```
\sbl_add_package_main_class{Defines, \details dihedrals}
```
we will get the replacement:
```
\brief Defines \ilinebr \details dihedrals
```
but this leads to a number of warnings like:
```
warning: End of list marker found without any preceding list items
```
As the end of the brief description is here `\ilinebr` this is replaced in the definition by `\ilinebr.` (so with a `.`). We first have to strip the aritficial newlines at (the beginning and) the end end of the brief description before adding the `.`.
(Found as side effect of https://stackexchange.com/filters/57710/doxygen).
|
| |\ \ \ \
| | | | |
| | | | | |
Command \ilinebr remained
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having the alias:
```
ALIASES += sbl_add_package_main_class{4}="\addtogroup \1-ref-manual ^^ @{ ^^ \class \2 ^^ \brief \3 \4 ^^ @}"
```
for the comment block:
```
/**
\sbl_add_package_main_class{Molecular_potential_energy, T_Phi_psi_dihedral_angles_visitor,
Defines iterator over all successive pairs of dihedrals.,
\details Defines iterator over all successive pairs of dihedrals.
\tparam CovalentStructure The type of the input covalent structure
}
*/
```
we get the warning:
```
warning: the name '\ilinebr' supplied as the argument of the \class, \struct, \union, or \include command is not an input file
```
The problem was that the rule:
```
<ClassDocArg2>{FILE}|"<>" { // second argument; include file
```
took the `\ilinebr`, the rule:
```
<ClassDocArg2>{DOCNL} {
```
should habe been checked before.
(reported as: https://stackoverflow.com/questions/63710433/doxygen-alias-with-arguments-the-classical-linebr-problem)
|
| | |_|/
|/| | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Also fixed a few VHDL related memory leaks and one newly introduced
Fortran memory leak.
|
| |\ \ \
| | | |
| | | | |
issue #6442 C++: Trailing return type syntax + void
|
| | | | |
| | | |
| | | |
| | | | |
corrected typo
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having:
```
/*!
* \brief Performs some side effect
*/
auto side_effect_after() -> void {}
```
We get the warning:
```
warning: return type of member side_effect_after is not documented
```
as the trailing return type was not taken into consideration.
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Also replaced tabs by spaces and removed trailing whitespace
And fixed line counting issue.
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8015
|
| | | |/ / /
| | | | |
| | | | |
| | | | | |
The pattern `\ilinebr` is actually also a line break, but was not handled.
|
| |/ / / / |
|
| | | | |
| | | |
| | | |
| | | | |
Also replaced tabs by spaces and removed trailing whitespace
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8017
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Handle `{` and `;` inside, nested, round brackets not as end of return type
|
| | | | | | |
|
| |/ / / / |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having the input
```
/*!
* \brief Performs some side effect
* \param i1 first */
auto side_effect_after(int i1, int i2) -> void;
```
we get the warning
```
warning: The following parameter of side_effect_after(int i1, int i2) -> -> void is not documented:
```
so a double "->".
The "->" has already been added in scanner.l and defargs.l so shouldn't be added here.
(also the return type gives a warning, but this is another issue #6442)..
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Readability of warning message
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A warning like:
```
warning: source examples is not a readable file or directory... skipping.
```
is hard to understand, would be better to have:
```
warning: source 'examples' is not a readable file or directory... skipping.
```
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The map construct runs apparently not through `id` but through `name` and thus breaking here the possibility to link
Also have `name=` use the `correctId`.
This is a regression on #7840
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |/ /
| |
| |
| | |
the `\ilinebr` (internal line break) should be properly be separated from previous text.
|
