| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
Avoid adding a space
|
| |\
| | |
| | | |
correct typo in comment
|
| | | |
|
| |\ \
| | | |
| | | | |
Bug 792727 - unescaped double quote in searchdata.js breaks search box functionality
|
| | |/
| | |
| | |
| | |
| | |
| | | |
functionality
Escaped the doubele quote.
|
| |\ \
| | | |
| | | | |
Small clarification for REFERENCED_BY_RELATION
|
| | |/
| | |
| | |
| | | |
Based on stack overflow question "Track C variable doxygen" (https://stackoverflow.com/questions/48586670/track-c-variable-doxygen)
|
| |\ \
| | | |
| | | | |
Bug 792415 - Blank rows on class page when using external tag file
|
| | |/
| | |
| | |
| | |
| | | |
Regression on: Bug 743367 - Duplicate attribute (target="_top" target="_top") generated in .SVG files
Added missing closing >.
|
| |\ \
| | | |
| | | | |
Bug 792935 - error: Could not open file .../doc/html/functions_ .html for writing
|
| | |/
| | |
| | |
| | |
| | |
| | | |
writing
Labels are used internally in pages but also for filenames and not all file systems can cope with all characters, so only ASCII printable characters are left untouched.
|
| |\ \
| | | |
| | | | |
Bug 638606 - Support for C# nullable type
|
| | |/
| | |
| | |
| | | |
Added, basic, support for C# nullable types.
|
| |\ \
| | | |
| | | | |
Bug 793052 - C#: Incorrect parsing of property definitions containing "//" symbols in one line with "}
|
| | |/
| | |
| | |
| | |
| | |
| | | |
symbols in one line with "}
The handling of comment signs inside a string for property definitions has been corrected, by defining parsing rules for these cases so that not the default comment handler will be used (i.e. remove the part behind the comment sign).
|
| |/ |
|
| |\
| | |
| | | |
-Fixed: some of remained work to support RTL in HTML output
|
| | |
| | |
| | |
| | | |
- Removed: support RTL form Return section in html, for consistency with parameter sections
|
| | | |
|
|/ / |
|
| |
| |
| |
| | |
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.
|
|\ \ \
| | | |
| | | | |
XML output: avoid warnings with scoped enum values in anonymous namespaces
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a C++11 `enum class` was present in an anonymous namespace (usually
in *.cpp files), the XML output was emitting warnings similar to the
following:
Internal inconsistency: member False does not belong to any container!
And the XML output was rendering bogus IDs for enum values starting with
`dummy_`, such as:
dummy_1a96ab6574751fdf6a53ceec8a3896c45daf8320b26d30ab433c5a54546d21f414c
The fix is to call memberOutputFileBase() on the enumeration itself and
not on the enum value, that way it provides correct file base that
corresponds to file base of the enumeration. There's also a new test
that checks this.
Note: this assumes that enum values belong to the same compound as enums
themselves. In my experience that was always the case and there's no
broken test after this change, so I hope I didn't break anything.
|
|\ \ \ \
| |/ / /
|/| | /
| | |/
| |/| |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
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,::::::).
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
template
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Physical newlines in ALIASES configuration tags.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some commands read input till the end of the physical line. In case these commands are used in an alias the rest of the line is lost / gives not the required results.
This patch creates the possibility to have physical newlines in ALIASES.
See also: https://stackoverflow.com/questions/46050789/doxygen-alias-with-multiple-commands
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix not initialized pointer when parser is starting on a new file.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The pointer oldEntry holds the last value of VhdlParser::current and is
compared to detect comment blocks that belong together. This could lead to
false positives when a new file is parsed and the new entry in
VhdlParser::current has by change the same pointer value as the old entry.
Doxygen warning like "warning: Found unknown command `\brief'" are the
consequence that leads to concatenated brief and detailed description in
the resulting output.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Allow case insensitive file pattern matching based on CASE_SENSE_NAMES
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Changed the navtree collapsed list icon to be more symmetric to the expanded list icon
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Properly copy images for the XML output
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use the exact same mechanism that is used for the HTML/LaTeX/... output,
which is findAndCopyImage() in docparser.cpp, because that one works,
unlike the method here. Not sure why that function doesn't handle XML as
well. Also not sure how to integrate this into the automated tests.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Full support for strong and typed enums in the XML output
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
There's a new boolean `strong` attribute on the `<memberdef>` element
that defines whether the enum is a classic or a strong one.
Tests were updated to verify both cases.
|