| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Problem with `<hr>` in LaTeX multicolumn cell
|
| |
| |
| |
| | |
Small problem with defining `\hrulefilll`, moved code.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have a `<hr>` in a table cell then it is displayed as a horizontal line (in LaTeX) unless it is in a multicolumn cell. In the later case it throws an error:
```
! You can't use `\hrule' here except with leaders.
\DoxyHorRuler ... }{0ex plus 0ex minus 0ex}\hrule
```
We have to use use `\hrulefill` in a table but in combination with the table option of xcolor this gives some problems so a new command has to be defined for this.
See also:
- horizontal rule / line inside a multicolumn field (https://tex.stackexchange.com/questions/506211/horizontal-rule-line-inside-a-multicolumn-field)
- interaction between \usepackage[table]{xcolor} and \hrulefill (https://tex.stackexchange.com/questions/506221/interaction-between-usepackagetablexcolor-and-hrulefill)
|
| |
| |
| |
| | |
preceding '|' action
|
|\ \ |
|
| | | |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7248
|
| | |
| | |
| | |
| | | |
Ignore automatically generated anchor names when importing a tag file.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| |\ \ \
| | | | |
| | | | | |
Adding JAVACC_FLAGS for javacc compilation
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
During transition to cmake build the, essential for debugging, flag possibility was not added.
(Added analogous to LEX_FLAGS and YACC_Flags).
Available debug options (according to old Makefile):
`-debug_parser`
`-debug_token_manager`
`-debug_lookahead`
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
|
| |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7436
|
| | | | |
| | | | |
| | | | |
| | | | | |
Added some documentation
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
The search for `/*` or /*!` ended at the last `*/` in a file and thus skipping other intermediate block end and new starts. Also the intermediate code was lost see as comment.
The filter pattern used was incorrect and should have been `<"/*" (~["*"])* "*" ("*" | ~["*","/"] (~["*"])* "*")* "/">` (thanks to https://javacc.org/contrib/C.jj).
Here also the space plus one or more `*` at the end beginning of the line are still incorporated as well as multiple `*` before the colosing `*/` this is also filtered.
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| |\ \ \
| | | | |
| | | | | |
issue #7313 VHDL attribute 'subtype is not supported and breaks parser
|
| | | | |
| | | | |
| | | | |
| | | | | |
Add the `'subtype` construct for variables etc.
|
| |\ \ \ \
| | | | | |
| | | | | | |
Email address seen as code starter
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some email addresses give problems in the comment converter as they contain e.g. `@code`, so we try to detect Email addresses (analogous to doctokenizer.l) to prevent these false positives.
The given warning would ne like:
```
aa.h:13: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 1)
```
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Incorrect NCName in docbook citations
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In a bibtex reference it is possible to have a colon as the id, but in docbook this will result in:
```
docbook/citelist.xml:5: validity error : xml:id : attribute value _citelist_1CITEREF_pre:post is not an NCName
<varlistentry><term><anchor xml:id="_citelist_1CITEREF_pre:post"/>[1]</term>
```
So the id has to be translated. A colon in an id can only happen in case the names is provided from the outside.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix incorrect reference resolving of enum class values
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When they share enum value names inside the same namespace.
This is a proposed fix for issue #7427: "Incorrect resolving of
references to enum class values with shared names inside the same
namespace"
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
the content
|
|\ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Coverity uninitialized
|
| | |\ \ \ \ \ \ \
| | |/ / / / / / /
| |/| | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Fixing a number of uninitialized variables based on the coverity output of November 30, 2019
|
|\ \ \ \ \ \ \ \ \
| |/ / / / / / / /
|/| | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | | |
virusxp-memory_leakage_fix
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
namespace
Fixing some memory issues caused by not correctly freed pointers
|
| |_|_|_|/ / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | | |
free issues
|
| | | | | | | | |
|
| |_|/ / / / /
|/| | | | | | |
|
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Textual error
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Correcting textual error
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Correct style in table header in case of paragraph is used
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In case a paragraph is used in a table header (quite unusual but can happen with 2 lines and an empty line in between), a `<p class="starttd">` tag is added and therewith the layout is incorrect.
This problem was detected based on #7409
This has been corrected (and tested with some available browsers FF, IE, Chrome, Opera).
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Adding some links in search documentation
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The search chapter was missing some links
|