| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
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).
|
| | | | |
|
|\ \ \ \
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
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 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
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
DGA45-Rel_1_8_20_DGA
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | | |
Fix ANSI-C anonymous (unnamed) struct/unions duplicated names issue
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Replace the respective characters by an underscore.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Documentation correction for CASE_SENSE_NAMES
|
| | | | | | |
| | | | | | |
| | | | | | | |
added missing "be"
|
| | | | | | |
| | | | | | |
| | | | | | | |
Did rephrasing things a bit.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In issue #8129 the problem of using different case of filenames was addressed, though in the documentation it was not clear what this meant for input files.
This has been corrected (the underlying problem has been handled with different other commits a.o. 2b5a4541fb6f806c02a1f6e65a1ff2610f29751f ).
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
64-bit Windows compiler warnings doctokinizer.l
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Removing compiler warnings like:
```
.../src/doctokenizer.l(101): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
.../src/doctokenizer.l(844): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data
...
```
(analogous as done in e.g. `commentscan.l`)
|
| |/ / / / / /
|/| | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
iterators
|
| | | | | | | |
|
|/ / / / / / |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
issue #8144 Problem with `\\` at end of an ALIASES in the configuration file
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In principle a configuration file should not know anything about the doxygen commands, but the handling of the escaped `\` and `@` are an exception of this rule (especially in `ALIASES`).
The mentioned escaped characters were not handled properly.
|
|/ / / / / / / |
|
|/ / / / / / |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_aliases_cmd
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When we have an command like `\\`, `\@`, `@@` or `@\`in ALIASES this should not disturb the recognition of the replacement strings like `\2`, so e.g. `\\2` should not be replaced by `\y` but remain `\\2` (assuming the `\2` is linked to `y` in an ALIASES).
This issue was found after #8137 had been fixed and was already present in older versions as well.
|
|/ / / / / / |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As indicated in the issue the proposed fix fixes OP's problem (according to his initial tests) as well as the problem in the CGAL documentation.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
issue #8130 Markdown relative links - not working for other folders
|