| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\ |
|
| | |\
| | |
| | | |
Extra settings for MathJax V3
|
| | | |
| | |
| | |
| | | |
For support of the `\eqref` command (used in CGAL) in MathJax V3 a small change has to be made (for a rationale see the discussion on https://groups.google.com/g/mathjax-users/c/oS0yQLb5BMk)
|
| | |\ \
| | | |
| | | | |
issue #8564 input buffer overflow, can't enlarge buffer because scanner uses REJECT
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
REJECT
When we have a very large "LONGSTRINBLOCK" (e.g. a very large documentation part or an encode executable in e.g. base64 encoding) , there are a lot of lines that have to be read at once, this is not really necessary they can be read sequentially (probably at the cost of some speed)
|
| |/ /
| |
| |
| | |
- Also updated GHC's filesystem.hpp to version v1.5.6
|
| | |
| |
| |
| | |
base compound not resolved under certain conditions (part 3)
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
|
| | | | |
|
| | |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_predefined_space
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having in the settings:
```
PREDEFINED += "HELP_DOT_SPACE( xs , ys , ... )=enum class xs { ys, __VA_ARGS__}"
```
we expect that the result is similar to when using a PREDEFINED setting:
```
#define LOC_SPACE( xs , ys , ... ) enum class xs { ys, __VA_ARGS__}
```
this is not the case especially due to the space after the last named argument.
We see that when we have:
```
LOC_SPACE(locSpace2, last);
```
we get
```
enum class locSpace2 { last }
```
and when having:
```
HELP_DOT_SPACE(dotSpace2, last);
```
we get:
```
HELP_DOT_SPACE (dotSpace2, last)
```
|
| |/ /
| |
| |
| | |
base compound not resolved under certain conditions (part 2)
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
Empty class definition.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In e.g. the HTML output of the doxygen documentation, chapter about formulas we see:
```
<p class="">
```
this is a regressing due to commit:
```
Commit: bb89b8136ff835c8fbd9f313d58815c8f361dff9 [bb89b81]
Date: Thursday, March 4, 2021 9:14:49 PM
Refactoring: some cleanup and removed text direction logic
```
made test now so that no empty class can occur.
|
| | |\ \ \
| | | | |
| | | | | |
Inconsistent behavior between unknown command and unknown html entity
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having:
```
/**
* an unknown command \unkn
*
* an unknown html entity \
*/
void fie();
```
we get the, correct, warnings:
```
warning: Found unknown command '\unkn'
warning: Unsupported symbol \ found
```
but contrary to ``unkn` the text for `\` is not echoed to the output.
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- avoids a second regEx
- compute ds.substr part only once
- unify varArgs only and fixed+varArgs cases
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8542
|
| | | | |
| | | |
| | | |
| | | | |
The variadic macro was not handled in case there were fixed arguments as well.
|
| | | | |
| | | |
| | | |
| | | | |
base compound not resolved under certain conditions
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Incorrect handling normal C comment in comment converter
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In normal C-comment (i.e. `/*` without extra `*` of `!` etc.) doxygen commands should be ignored.
This was notr te case see e.g.:
```
const char * /* O - or @code NULL@ */
zipcXMLGetAttribute();
```
|
| | |\ \ \ \ \
| | |/ / / /
| |/| | | | |
Issue #8556 Removed bracket '(' in HTML an XML output
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
The opening bracket was "forgotten" when the sharp count > 0 (in this case 1). the closing bracket was later on added to the name so the opening bracket is also be added to the name.
|
| |/ / / / |
|
| | |_|/
|/| |
| | |
| | |
| | | |
For easier debugging one can do e.g. `{% msg %}value={{ variable }}{% endmsg %}`
to list the value of a variable also when it is a list or struct.
|
| | | | |
|
| |\ \ \
| | |/
| |/| |
|
| | |\ \
| | |/
| |/| |
Formulas with a new environment handled as inline formulas
|
| | |/
| |
| |
| | |
As a regression of #8509 formulas that start a new environment (`\f{`) were considered as inline formulas as teh inline test looked for a `\{` but should look for `\begin{`.
|
| |/ |
|
| |
|
|
|
| |
- This new page layout is only enabled if DISABLE_INDEX=YES, GENERATE_TREEVIEW=YES,
and FULL_SIDEBAR=YES.
|
| |\ |
|
| | |\
| | |
| | | |
Adding field extern for sqlite output
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have:
```
extern int var;
```
the `extern` was not recorded in case of sqlite output.
|
| | |\ \
| | | |
| | | | |
Missing page when followed by mainpage
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we have in one file a `\page` followed by a `\mainpage` than this page is not shown / completely ignore, an example:
```
@page pg_tst_1 Test 1
the 1 page
@mainpage Test MainPage
the mainpage
```
this problem is due to the fact that `handleMainPage` is called when a `\mainpage` command is found, and this is also the case at the end of the content of `\page` resulting in the fact that the name of this page is removed (and thus actually the complete page).
|
