| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
XHTML: div tag not possible as part of a p tag.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With test 76 we get a number of messages like:
```
element p: validity error : Element div is not declared in p list of possible children
```
this is a regression on issue #8169 / pull request #8170.
The `<div>` tag is not allowed as child of a `<p>` tag and furthermore in the output when a number of items should be on one line this is not the case anymore.
This all can be corrected by means of using the `<span>` tag instead of the `<div>` tag.
|
|\ \
| | |
| | | |
issue #8186 Path resolving breaks on included @ sign
|
| | |
| | |
| | |
| | | |
Add in the `@` sign as possible character in a FILEMASK
|
|\ \ \
| | | |
| | | | |
Incorrect line count in case of an error in msc input
|
| | | |
| | | |
| | | |
| | | | |
The variables to store line number etc. are static variables and should be reset on each invocation of the lex msc parser.
|
|/ / / |
|
|\ \ \
| |/ /
|/| | |
Silently ignoring unexpected characters in configuration
|
| | |
| | |
| | |
| | | |
Should also ignore `\r` as white space
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having a doxygen configuration file like:
```
QUIET=YES
@INPUT = file
@UNKNOWN =
@UNKNOWN1
@UNKNOWN 1
@UNK # test
```
we get the warnings
```
warning: ignoring unsupported tag 'UNKNOWN' at line 3, file Doxyfile
warning: ignoring unknown tag 'UNKNOWN1' at line 4, file Doxyfile
warning: ignoring unknown tag 'UNKNOWN' at line 5, file Doxyfile
warning: ignoring unknown tag '1' at line 5, file Doxyfile
warning: ignoring unknown tag 'UNK' at line 6, file Doxyfile
# Difference with default Doxyfile 1.9.0 (fa65bb38f81457d00f9c900bb57eb68bea59b1b4)
QUIET = YES
INPUT = file
```
especially the missing of a warning about the `@` in `@INPUT` can be a bit misleading (it might be that the user wanted to use `@INCLUDE` and and specified `@INPUT`
It would be better to have a warning about a not handled character instead of just ignoring it.
|
| | |
|
|\ \
| | |
| | | |
Missing commands in list of commands documentation
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At the top of the chapter describing the commands there is a list with described commands, here the commands:
```
\noop
\static
```
were missing.
|
|\ \ \
| |/ /
|/| | |
Redundant storage of `VhdlParser_adj.cc`, it can be regenerated
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Misspelling in the directory name:
```
${PROJECT_SOURCE_DIR}/VhdlParser/vhdl_adj.py
```
should be
```
${PROJECT_SOURCE_DIR}/vhdlparser/vhdl_adj.py
```
(Not uppercase V and P in directory name).
|
|/ /
| |
| |
| |
| | |
The file `VhdlParser_adj.cc` is independent of the javacc program, it is just dependent on `VhdlParser.cc` (and `vhdl_adj.py`) and therefore can be regenerated at any time.
It is better to regenerate it (and store it) into `generated_src ` in stead of in the repository.
|
|/ |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Unclear description of QHG_LOCATION
|
| | |
| | |
| | |
| | |
| | | |
The description of `QHG_LOCATION` is a bit unclear (compare with `HHC_LOCATION`).
(based on https://stackoverflow.com/questions/64795335/qhelpgenerator-with-doxygen-keep-showing-sh-1-permission-denied/64801829#64801829)
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Show QT version in doxywizard
|
| |/
| |
| |
| | |
When debugging problems in respect to the doxywizard it always good to know with which version the doxywizard has been build a which runtime version is being used(especially when not linking statically)
|
|\ \ |
|
| |\ \
| | | |
| | | | |
issue #8169 "\emoji heavy_check_mark" produces ✓ instead of ✔️
|
| | |/
| | |
| | |
| | | |
Create the possibility to change the used font for an emoji (the default is unchanged, but an example is given of how it is used at the site: https://unicode.org/emoji/charts/full-emoji-list.html).
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| | | |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doxyw_docu
|
| | |
| | |
| | |
| | | |
Bringing the doxywizard documentation up to date with the current version.
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| |\ \
| | | |
| | | | |
Doxygen crashes on Fortran
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having a Fortran file like:
```
!> module docu
MODULE test_mod
INTERFACE
!> @brief iets
SUBROUTINE subr_i(this)
INTEGER this
END SUBROUTINE subr_i
END INTERFACE
!< @brief type brief
TYPE, PUBLIC :: test_type
!> docu
integer i
END TYPE test_type
END MODULE test_mod
```
this is due to the fact that a incorrect start of comment `!<` is used for the `TYPE` and that initiated because the last `SUBROUTINE` argument does not have any documentation.
The actual cause is that at the end of a subroutine the `vtype` is not properly reset.
|
| |\ \
| | | |
| | | | |
Typo in namespacedef.h
|
| |/ /
| | |
| | |
| | | |
Typo in namespacedef.h as found by Fossies
|
|/ / |
|
|/
|
|
|
|
| |
Split Definition/ClassDef/NamespaceDef/MemberDef into a immutable and mutable part
Aliases are immutable, other symbols are stored using an immutable
interface but can be made mutable explicitly by dynamic casting.
|
|\
| |
| | |
Incorrect handling of string with spaces and no quotes
|
| |
| |
| |
| | |
Correcting some (Cygwin) compilation warnings / errors
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During some tests on the documentation of LLVM the (CMake generated) doxygen configuration file contained the line:
```
DOT_PATH=D:\Program Files (x86)\Graphviz2.38\bin\dot.exe
```
and this was interpreted by doxygen as
```
DOT_PATH = D:\ProgramFiles(x86)\Graphviz2.38\bin\dot.exe
```
without any message other than that later on the `dot` executable could not be found.
It is clear that here the double quotes were missing.
This problem has been solved by giving a warning and setting the value to the default value.
- configimpl.l
- config_doxyw.l
during the checking some debug facilities for the doxywizard were required and this has been implemented:
- config_doxyw.l
- doxywizard.h
- doxywizard.cpp
it was also discovered that in case of none existing int or bool values were specified the wrong "defaults" were taken (it was set to `0` / `false`), now the correct defaults are taken
- inputbool.cpp
- inputint.cpp
|
|\ \
| | |
| | | |
Warnings in generated VhdlParser.cc
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When compiling the generated VhdlParser.cc we get a number of warnings about the return type, these are no problems as they all follow an assert(false) but when "promoting" the missing to return type warning to an error (openSUSE) this is a problem.
The best way would be that the problem is solved in javaCC though this will be probably a long process, so we use the workaround to overcome the problem.
(The problem was detected as part of the reproducibility tests for openSUSE, see #8158)
|