| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Warnings in case of a VHDL error
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having a vhdl construct like:
```
entity _H_ is
```
we get the, a bit unclear, warnings like:
```
Lexical error at: 16:8. Encountered: _ after: .
```
with version 1.8.17 we got the warning:
```
.../vhdl.vhd:16: warning: Lexical error, Encountered: '_' after: ''
```
not 100% clear either but at least clear which file is involved and what the meaning of the '16' is.
Also the message didn't conform the doxygen style / place / handling of warnings / errors anymore (didn't go to the WARN_LOGFILE anymore).
(The message is correct as a vhdl identifier cannot start or end with an underscore.
Between the used javaCC versions (now 7.05) and the previously used version 6.xx apparently a small in the error handler prototypes has been introduces, and thus not finding the doxygen version anymore.
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
issue #7558 PlantUML: Different behavior whether LATEX_OUTPUT has a final slash or not.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
slash or not.
The problem is that full qualified paths in `*_OUTPUT` were not handled properly they were handled as it were relative paths.
In the documentation it is stated for e.g. LATEX_OUTPUT:
> The LATEX_OUTPUT tag is used to specify where the LATEX docs will be put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put in front of it.
So in case of a non relative path the given path should be used and this path can be unrelated to `OUTPUT_DIRECTORY`, so we have to store the designated output path as well.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Remove some unused enums in doxywizard
|
| | | |/ / /
| | |/| | |
| | | | | |
| | | | | | |
Remove some unused enums in doxywizard
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Doxywizard unknown configuration enum values
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
Analogous to pull request #7586 a wrong value is given check e.g `OUTPUT_LANGUAGE = dutch`
|
| |\ \ \ \ \
| | |/ / / /
| |/| | | | |
issue #7590 Map .f18 filetype to Fortran
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Documentation has to be updated as well
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Supporting f18 extension
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | | |
Added development option to use inkscape to create SVG formulas.
|
|\ \ \ \
| | | | |
| | | | | |
Unknown configuration enum values
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we set for instance `DOT_IMAGE_FORMAT = SVG` (and generate call graphs) we get messages from the `dot` tool like:
```
error: Problems running dot: exit code=1, command='dot', arguments='".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.dot" -TSVG -o ".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.SVG"'
```
on other places (e.g `HTML_FORMULA_FORMAT`) and an unknown or enum value with a wrong case, the default value is (silently) taken.
We now check:
- is the enum value of the correct case otherwise (silently) set it to the correct case.
- in case of an unknown enum value a warning is given and the default value is used
|
| | | |
| | | |
| | | |
| | | | |
Also added option HTML_FORMULA_FORMAT to generate SVG files for images (requires pdf2svg)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
void and virtual void functions
|
|\ \ \ \
| | | | |
| | | | | |
vhdl-fixed-bug-7432
|
| |\ \ \ \ |
|
| | | | | | |
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Problem with links from search index files
|
| | | |_|/ / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The format of the tag file has been slightly changed in the past so that the original HTML_FILE_EXTENSION was preserved by adding the HTML_FILE_EXTENSION to the items in the tag file.
This change has not been reflected in the search files like `files_0.js` resulting in lines like
```
['core_5fbigfloat_2eh_8971',['CORE_BigFloat.h',['../../Number_types/CORE__BigFloat_8h.html.html',1,'']]],
```
this has been corrected.
(Found in the CGAL code).
|
| |\ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
More indicative warning for wrong nesting of sections
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
In case we have a "*section" outside the hierarchy it is useful also have the id of the misbehaving "*section" even though line numbers are given , they might be misleading.
|
|/ / / / / |
|
|/ / / / |
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Correct handling of error / removed debug statement
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In the vhdldocgen:
- error should be handled in a doxygen consistent way (in this case with an err call)
- removed left over debug statment (found through #7528)
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
More accurate warning message.
|
| | | |/ / /
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
in code like `this command @unkn` would give (whilst all information is present)
```
warning: Found unknown command '\unkn'
```
instead of
```
warning: Found unknown command '@unkn'
```
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
and other small fixes
|
| |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_791390
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
- added possibility (and checks) for xml
- added missing case for class in docbook
|
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
use explicit constructor' issue on some versions of gcc.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|