| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Implementation of the C++2x three-way / spaceship operator.
|
|/
|
|
|
|
|
|
| |
When having a very long initialization line in php code we get the message:
```
input buffer overflow, can't enlarge buffer because scanner uses REJECT
```
In this case the, easy, solution is to split, in the lexer, the input based on the commas.
|
| |
|
| |
|
|
|
|
|
| |
In some cases performance dropped when upgrading from version 1.8.16 to 1.8.17 or 1.8.18.
With these changes the performance should be back to normal again.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I issue #7060 and example was given with
```
typedef const char m_msgEvtName;
```
we see that
- 1.8.15, listed under Typedefs:
` typedef const char m_msgEvtName`
- 1.8.16 and up, listed under Variables:
`const typedef char m_msgEvtName`
so mentioned:
- wrong "header"
- const at the wrong place
This is a regression on:
C# consts incorrectly placed under instance variables (Origin: bugzilla #535853) (issue #2976)
and the pull request #7048
The fix should only be used for C#
|
|
|
|
| |
not recognized as a function (Origin: bugzilla #792830)
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Consistency `\*only` and `\end*only` commands
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like:
```
.../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag!
../.aa.h:4: warning: rtfonly section ended without end marker
.../aa.h:4: warning: rtfonly section ended without end marker
```
in case of a problem like:
```
/** \file
* \rtfonly
* RTF /* Nested */
* \endrtfonly
*/
```
|
|/
|
|
| |
silently ignored
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We get warnings like:
```
warning: reached end of file while yyextra->inside a 'code' block!
warning: Ignoring \brief command yyextra->inside argument documentation
```
this is due to the fact that the scanner has been made reentrant (inside becomes yyextra->inside and this slipped into the warning strings as well)
|
| |
| |
| |
| | |
the content
|
| |\ |
|
| | |
| | |
| | |
| | | |
free issues
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
Fixing a number of uninitialized variables based on the coverity output of November 30, 2019
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix for issue #7393
When closing a group on multiple lines, like:
/*! @}
*/
The line count of subsequent lines is wrong (it's one line less than it
should be).
|
| | |
|
| |\
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7295
|
| | |
| | |
| | |
| | | |
documentation has to be added to the "last" entry not to the "first" / "top"
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Spelling corrections as found by codespell and in #561.
Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.):
- "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...)
- "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
|
| |\ \
| | | |
| | | | |
issue #7358: Ternary conditional and null-coalescing operator in constructor results in faulty warning
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
results in faulty warning
Problem due to the implementation of "Support for C# nullable types (Origin: bugzilla #638606)" (issue #4064, pull request #645). The used condition was a bit to stringent so later on the function was not recognized as constructor.
|
| | | | |
|
| | | | |
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have a problem like:
```
/** \file
* ```
* router = (new Router());
* ```
*/
```
there is no problem, but as soon as we add a space somewhere before the start or end identifier of the fenced code block we get:
```
.../aa.h:6: warning: reached end of file while inside a '```' block!
The command that should end the block seems to be missing!
```
i.e. a problem like:
```
/** \file
* ```
* router = (new Router());
* ```
*/
```
or
```
/** \file
* ```
* router = (new Router());
* ```
*/
```
The relevant length is the length identifying the fenced code block / number of back ticks, not the number of spaces in front of it (analogous number of tildes).
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
Bug 570798 - \\\< does not work for php constants
|
| | |/
| | |
| | |
| | | |
Handle comment for define analogous to a normal php variable, the closing part is automatically done when the comment is finished (rule: `<DefinePHPEnd>";"`).
|
| |\ \
| | | |
| | | | |
issue 7302: Parsing of template args in single-quotes is incorrect.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we encounter an unescaped single or double quote during specialization we search for the closing quote.
We are cionnsidering potential escape sequences in the strings as well.
|
| |\ \ \
| | |/ /
| |/| | |
Fix typos
|