| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
contains a \code block
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_783134
|
| |
| |
| |
| |
| |
| |
| | |
contains a \code block
General problem regarding having a code / verbatim section inside a table.
Besides handling of the $ some other characters need special handling as well as the \n.
|
|\ \ |
|
| |/
| |
| |
| | |
HTML output
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* src/doctokenizer.l: add VARARGS, aka variadic function args '...'
* src/util.cpp (linkToText): call substitute() with skip_seq set to 3
to keep each '...' sequence of chars unchanged
For instance, the command '@ref fun(int,...)' now is able to parse
each '...' sequence of chars correctly to reference fun(int,...).
Before this patch, the '...' part was skipped.
Also, linkToText() is fixed to not substitute '...' with '::::::' in
the text representation of the link.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* src/util.h (substitute): add skip_seq to function declaration
* src/util.cpp (substitute): implement skip_seq to keep unchanged a
given number of sequential chars otherwise targeted for substitution
* src/util.cpp (resolveRef): call substitute() with skip_seq set to 3
to keep each '...' sequence of chars unchanged
For instance, the command {@link fun(int,...)} now keeps each '...'
sequence of chars unchanged to reference fun(int,...). Before this
patch, each '.' was substituted into '::' by resolveRef() calling
substitute(), producing a weird reference to fun(int,::::::).
|
|\ \
| | |
| | | |
Allow case insensitive file pattern matching based on CASE_SENSE_NAMES
|
| | | |
|
|/ /
| |
| |
| |
| | |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
| |
| |
| |
| | |
It has refcounting, copy-on-write and all, but this is still better.
|
| | |
|
| | |
|
|/
|
|
| |
Corrected handling of (local) variables as functions as well as handling of non Fortran variables used in Fortran code.
|
|
|
|
|
|
| |
some doxy typos and some misc. source typos
typos
some doxy typos and some misc. source typos
|
| |
|
| |
|
| |
|
|
|
|
| |
argument type
|
|
|
|
| |
Documentation section
|
| |
|
|
|
|
|
|
| |
When looking at the index of the doxygen (pdf) manual we see that __init__ is on a bit strnge place (between "\" items) and that the item "\@" is missing.
Made handling of the index consistent by using latex... routines and adjusting the label routine in respect to the @.
|
|
|
|
|
| |
Purpose to have the possibility to have repeating texts not repeated in the comments.
The commands include and snippet introduce code blocks whilst the commands includedoc and snippetdoc inclode the text as is and it will be parsed by doxygen.
|
|\
| |
| | |
Also map .f95, .f03 and .f08 file types to Fortran
|
| |
| |
| |
| | |
These are for Fortran 95, Fortran 2003 and Fortran 2008, respectively.
|
|/ |
|
|
|
|
| |
formula.cpp handles package arguments correctly
|
| |
|
|\
| |
| | |
Bug 751984 - Use UTC timezone when displaying QDateTimes parsed from SOURCE_DATE_EPOCH
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SOURCE_DATE_EPOCH
According to the SOURCE_DATE_EPOCH spec [1], "Formatting MUST be deferred until runtime if an end user should observe the value in their own locale or timezone."
However setTime_t uses localtime, so the output is in the timezone of the build machine running doxygen, and not the timezone of the reader consuming the final output.
To adhere to the spec, the easiest option is to add a setTimeUtc_t function that is the same as setTime_t, but only uses gmtime instead of first trying localtime.
[1] https://reproducible-builds.org/specs/source-date-epoch/
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
In case of windows 64 bit the generation of the doxygen documentation results in a pop up screen with (most relevant information):
Debug Assertion Failed
File: f:\dd\vctools\crt\crtw32\convert\istype.c
Line: 68
Expression c >= -1 && c <= 255
Problem is that a value is fed to isspace that is not in the correct range and has to be converted to this range.
|
|\ |
|
| |
| |
| |
| | |
Besides the fact that the % sign was not escaped also the & was missing and had to be escaped as well.
|
| |
| |
| |
| | |
underscores were not escaped in the content for "PDF summary/index in the left tab"
|
|/ |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Bug 504305 - FILTER_PATTERNS won't take command with arguments
|
| | |
| | |
| | |
| | | |
INPUT_FILTER is a string so multiple values are read till the end of the line and quotes are automatically removed. FILTER_PATTERNS and FILTER_SOURCE_PATTERNS are list of strings so with multiple arguments for one extension quotes are mandatory, but they were not removed.
|
|/ / |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
improve performance
|
| |
|
|
|
|
| |
Added pyw as extension, based also on: https://docs.python.org/2/tutorial/appendix.html (15.1.2. Executable Python Scripts)
|
| |
|