| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
```
|
| |\ \ \ \
| | | | |
| | | | | |
Consistency in documentation of used Python versions
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
At some places Python version 2.6 was still mentioned, made uniform to 2.7 everywhere.
(Is already a bit dubious as of January 1st, 2020 Python 2.7 will reached the end of its life., but still a lot will have Python 2.7 by default).
|
| |\ \ \ \
| | | | |
| | | | | |
Not always linking in map as maps use name instead of id
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| | |
issue #7996 \ref commands broken in markdown tables
|
| |/ /
| |
| |
| | |
the `\ilinebr` (internal line break) should be properly be separated from previous text.
|
| |\ \
| | |
| | | |
issue #7995 Doxygen doesn't handle very simple example in the .md file
|
| |/ /
| |
| |
| | |
Besides "keep utf8 characters together..." as done for the C-type parser in code.l (commit d3d9dd8540ec159de080859c8f34a2581c4147f0) this also has to be done for the Fortran, SQL and VHDL code lexers. The code lexers for python and xml already didn't give errors as they already handled these cases for the example.
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
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 */$
```
|
| |/ / / |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7872
|
| | | | |
| | | |
| | | |
| | | | |
Not only the preprocessor suffered from the "problem" but also the source code (e.g. with `SOURCE_BROWSER`) gave some strange / missing results.
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | | |
(multi-thread input processing)
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_786382
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on the definition in the (informative) Annex A of the C++ draft 2020 standard (N4849, part [gram.lex]), the definitions have been made for the lexer.
Now integer and floating point constants wit a single quote are seen as numbers and not as part of character constants.
(also tested on CGAL)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Initialized member variables inside the class
- Added copy & assign operators for OutputGenerator and Derived classes.
- throw a runtime exception when OutputGenerator is copied while is file
is still in progress.
- Added clone method to make a copy of OutputList.
- Moved the implementation of enable() & disable() and friend into
OutputGen instead of having the same implementation in each derived
class.
- Made m_dir and m_fileName readonly (members dir() and fileName())
- Removed call to new while adding generators to OutputList
- Replaced QStack by std::stack for the "enabled" state.
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | | |
- reverted some of the change that introduced the problem
- fixed the original problem (#7216) in a different way
|
| |\ \ \
| | | |
| | | | |
issue #7970 Doxygen doesn't stop on errors
|
| |/ / /
| | |
| | |
| | | |
Routines doing their own formatting should also stop when `WARN_AS_ERROR` is set.
|
| |\ \ \
| | | |
| | | | |
Format for size_t (in e.g. warnings)
|
| |/ / /
| | |
| | |
| | | |
This one was a bit hidden in conditional compilation (see also #7966).
|
| | | |
| | |
| | |
| | | |
leak) (part 2)
|
| |\ \ \
| | | |
| | | | |
Format for size_t (in e.g. warnings)
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From the C standard paragraph 7.21.6.1 The fprintf function
```
z
Specifies that a following d, i, o, u, x, or X conversion specifier applies to a size_t or the
corresponding signed integer type argument; or that a following n conversion specifier
applies to a pointer to a signed integer type corresponding to size_t argument.
```
|
| |\ \ \
| | | |
| | | | |
Spelling correction
|
