| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
issue #8329 Force line buffering
|
| |
| |
| |
| |
| |
| | |
By default stdout is buffered when redirecting, the `-b` option of doxygen prevents this.
Removing non used variable `outputToWizard`.
|
|\ \
| | |
| | | |
issue #8336 Python class only with async methods support
|
| | | |
|
|\ \ \ |
|
| | | | |
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_typedef_code
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we have `typedef ::my_type T2;` the code coloring should be:
- typedef : keyword
- ::my_type : link
- T2 : link
though we see:
- typedef ::my_type : link
- T2 : link
this has been corrected.
Found by means of issue #8350
Note there might be other cases with the same problem as well.
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
issue #8511 Java: linebreak after @link can cause wrong parsing of subsequent doc
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
subsequent doc
Allowing also a `\n` after the @link.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
issue #8518 tag </programlisting> was inserted before </highlight> parsing cpp file to xml
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
cpp file to xml
The possible `\n` was not taken into account when codifying the line(s).
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
The problem was a bit deeper, it was also valid for other output formats.
Implemented the `type` and `start` attribute for all relevant output types.
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Warning from preprocessor regarding binary literals
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When having a line like:
```
#if (JITTERLISP_FIXNUM_TAG_BIN == 0)
```
with
```
#define JITTERLISP_FIXNUM_TAG_BIN 0b0000
```
we get the warning:
```
warning: preprocessing issue while doing constant expression evaluation: syntax error: input=' ( 0b0000 == 0)'
```
The equivalent hexadecimal / octal / decimal versions are OK, the handling for the binary was missing.
(Found by Fossies in the poke package).
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
issue #8505 Local search too specific
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
Added small explanation on searching in the documentation.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Error messages on ASSERTS
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Added missing `\n` in output, most likely regression due to change from the qt version of `ASSERT`:
```
qFatal("ASSERT: \"%s\" in %s (%d)",#x,__FILE__,__LINE__)
```
or
```
qWarning("ASSERT: \"%s\" in %s (%d)",#x,__FILE__,__LINE__)
```
In Fossies we got that the messages were just put behind each other (they should not appear at all but that is another issue):
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_lex_option
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- improved handling of `%option`
- multiple options on 1 line
- handling of unknown options that contain part of a handled option (like noreentrant)
- correction of definition yylex function definition, signature depends on usage of
- reentrant
- bison-bridge
- bison-locations (automatically include bison-bridge)
(found as part of some Fossies tests)
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
|/ / / / / / /
| | | | | | |
| | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_lex_rules
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- handling of square brackets, an opening square bracket inside a pair of square brackets has no special meaning unless followed by a colon (resulting in `[:...:]`.
- handling of sharp brackets so that `<tst><<<WORD` is correctly hanlded
- better handling of escaped charcters
- handling of `(?...)`
(Found during tests on some lex files available on Fossies).
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
issue #7346 Incompatibility with MathJax 3.0
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Implementing the possibility to use MathJax versie 3
- Added setting MATHJAX_VERSION
- made setting for MATHJAX_RELPATH so that is suited for version Mathjax version3, i.e. selecting right default
- made setting for MATHJAX_FORMAT so that is suited for version Mathjax version3, automatic conversion between MathJax 2 and MathJax3 format setting
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
issue #8518 tag </programlisting> was inserted before </highlight> parsing python file to xml
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
python file to xml
Doxygen expects that decorators don't have a return in them, but the complicated decorator:
```
@basetest.unittest.skipIf(
api_implementation.Type() != 'cpp' or api_implementation.Version() != 2,
'Errors are only available from the most recent C++ implementation.')
```
has some in them.
This leads to the mentioned problem as well as that the line counting is incorrect (we see that the last mentioned lie number in the xml file is 2964 though the file has 2966 lines). By fixing this (and also the line counting in the python scanner) the problem looks to be handled.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Fix typos
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
|/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- methods were marked const but still returned a non-const reference,
cause wrongly optimized code for some platforms/compilers
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
- stored value was overwritten probably due to compiler optimisation bug
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When GENERATE_TREEVIEW was enabled and the classlist was disabled in the
DoxygenLayout.xml
|
| | | | | | | |
|
|\ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Problem with Fortran, giving a warning about invalid state
|
| |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Fortran gives a warning like
```
Error in file .../mic_lib.f90 line: 15, state: 4(SubprogBody)
```
This happens after the upade:
```
Commit: 592aaa4f17d73ec8c475df0f44efaea8cc4d575c [592aaa4]
Date: Sunday, April 11, 2021 9:22:59 PM
Commit Date: Thursday, April 22, 2021 7:34:13 PM
Refactoring: remove implicit conversion from QCString to const char *
```
Looks like an initialization that was previously done automatic doesn't happen anymore.
(Problem found by Fossies in openmpi, gcc, fimex).
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
issue #8425 Would like a way to sort class list but not brief member list
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In the 1.9 series the sorting of the classes inside the namespaces was made dependent on the configuration setting `SORT_BRIEF_DOCS`, this is a regression compared to the 1.8.20 and earlier versions.
(see also the discussion in the issue #8425)
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Usage of default lex rule with `\param`
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In case we have a file like
```
/// \file
/// the fie
/// \param
/// arg the argument
void fie(int arg);
```
we get in the console output extra empty lines, this is due to the fact that the default lex rule kicks in an the output is echoed to the consol.
We have defined an explicit rule.
|