| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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`
|
|\ |
|
| |\
| | |
| | | |
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
|
| | | | | | | |
|
|/ / / / / / |
|
|\ \ \ \ \ \
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Problem converting UCS big endian file
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When having a file with a Big Endian BOM this is not always handled in a correct way when using the generic UCS-2 approach, using the explicit version works well.
(problems see with a gcc (SUSE Linux) 7.4.1 20190905 [gcc-7-branch revision 275407] and glibc-2.26-lp151.18.7.x86_64).
|
| | | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
warning.
|
| | | | | | |
|
| | | | | | |
|
|/ / / / / |
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Problem with horizontal ruler directly after fenced code section
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When having a fenced code block directly followed by a horizontal ruler like:
```
~~~
B
~~~
---
```
we get the warning:
```
bb.md:5: warning: unexpected command endcode
```
due to the fact that the markdown parser replaces the `~~~` by a `@code` / `endcode` block and then handles the horizontal ruler `---` but this is seen as a level 2 header on the previous part resulting in the markdown code:
```
@page md_bb bb
@subsection autotoc_md0 @code
B
@endcode
```
The problem also occurs when a fenced code block is created with back tics.
By adding a `\n` this problem is fixed.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
HHC and directory elements starting with "."
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Based on the question 'Doxygen failed to run html help compiler, hhc.exe error HHC5010 when running from folder that has a parent folder that starts with “.”/ (https://stackoverflow.com/questions/58861908/doxygen-failed-to-run-html-help-compiler-hhc-exe-error-hhc5010-when-running-fro).
In we https://social.msdn.microsoft.com/Forums/en-US/0681145c-223b-498c-b7bf-be83209cbf4e/issue-with-html-workshop-in-a-windows-container?forum=visualstudiogeneral see:
HTML Help 1.x command line compiler hhc.exe cannot compile CHM file to folder whose full path contains folder name starting with dot. If you have that problem, you probably specified output path with folder starting with dot, e.g. "d:\My files.NET\documentation". You can use dots in folder names but not at the beginning.
We first convert the current path to a short name path and set this as current directory, this is only done on Windows other systems are not touched.
|
|/ / / / / / |
|