| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
including the @ingroup marked classes in the generated documentation.
|
| |
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_789318
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Create possibility to see the CS construct `=>` not as an initializer (based on just the `=`) but as getter.
This problem solves besides this issue:
- #6278 c# expression-bodied property is not rendered correctly (Origin: bugzilla #789318)
also the issues:
- #6064 Lambda for read-only property in C# 6 (Origin: bugzilla #771283)
- #7550 C# Expression-Bodied Properties reveals underline implementation
- #7914 Doxygen Treats C# Inline-Bodied Properties as Member Variables
|
| | |
|
| |
| |
| |
| | |
Also replaced tabs by spaces and removed trailing whitespace
|
|/
|
|
| |
Handle `{` and `;` inside, nested, round brackets not as end of return type
|
|\
| |
| | |
bug_647654 Special command \fn fails when first argument of PHP function is call-by-reference
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
call-by-reference
The handling of `(&$var` for php was not included at all places.
It was handled with the rules (in scanner.l):
```
<FindMembers>"("/{BN}*"::"*{BN}*({TSCOPE}{BN}*"::")*{TSCOPE}{BN}*")"{BN}*"(" | /* typedef void (A<int>::func_t)(args...) */$
<FindMembers>("("({BN}*"::"*{BN}*{TSCOPE}{BN}*"::")*({BN}*[*&\^]{BN}*)+)+ { /* typedef void (A::*ptr_t)(args...) or int (*fun c(int))[], the ^ is for Obj-C blocks */$
```
|
|/
|
|
| |
(multi-thread input processing)
|
| |
|
| |
|
|
|
|
| |
Explicit counting of the removed newlines at the beginning of a documenation block (markdown.cpp) so this number can be added to get a better line number in case of warnings.
|
| |
|
| |
|
|
|
|
|
| |
And at the same time make sure it gives the same results as when
processed using a single thread.
|
| |
|
|\
| |
| | |
issue #7734 Incorrect parsing of Q_PROPERTY
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The parsing of the type / name was not done correctly as the name `{ID}` is also part of the `{TSCOPE}` and hence the name was seen as a type.
The name is the last part before an attribute is present.
Missing other parts:
- parsing of `*`
- not parsing of a number of (not supported attributes)
The definition of `Q_PROPERTY` is:
```
Q_PROPERTY(type name
(READ getFunction [WRITE setFunction] |
MEMBER memberName [(READ getFunction | WRITE setFunction)])
[RESET resetFunction]
[NOTIFY notifySignal]
[REVISION int]
[DESIGNABLE bool]
[SCRIPTABLE bool]
[STORED bool]
[USER bool]
[CONSTANT]
[FINAL])
```
Note: in the implementation we do not enforce the order of the attributes.
|
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| | |
|