| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\ |
|
| |\
| | |
| | | |
issue #7033 Syntax highlighting doesn't work when calling \dontinclude from Markdown files
|
| | |
| | |
| | |
| | |
| | |
| | | |
Markdown files
Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
|
|/ / |
|
| |
| |
| |
| | |
In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
|
|/
|
|
| |
Test 19 was incorrect, didn't show group description either (see make tests TEST_FLAGS="--keep --xhtml --id=19"
|
| |
|
|
|
|
|
|
| |
Create possibility to use CLANG_ASSISTED_PARSING, works only when doxygen has been compiled with "use_libclang"
Note at this moment the test suite gives an error, see issue #6948
|
|
|
|
| |
Added option `--xmlxsd` to check generated XML files against XSD in the doxygen tests suite.
|
|\
| |
| | |
Adjustment of xhtml1-transitional.dtd
|
| |
| |
| |
| | |
After small discussion conclusion was better to remove the obsolete `doxygen=`
|
| |
| |
| |
| |
| |
| |
| |
| | |
Adding attributes:
- doxygen
to be able to validate doxygen generated xhtml documents.
Analogous to #6681 but now for the area tag (found in the doxygen tag example).
|
|/ |
|
|\
| |
| | |
Double id for tooltips in XHTML possible.
|
| |
| |
| |
| | |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|/
|
|
| |
Update test
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_pre_markdown
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to the documentation:
Doxygen does not have this requirement, and will also process Markdown formatting inside such HTML blocks. The
only exception is <pre> blocks, which are passed untouched (handy for ASCII art).
Though in case the `</pre>` is the last statement in a non block type comment the markdown is processed. C has block type /* ... */ and /// is translated to this, Fortran, Python are line type comments.
Adding a `\n` at the when no `\n` is present at the end solves the problem.
|
| | |
|
|\ \ |
|
| |/
| |
| |
| | |
Test case.
|
|/
|
|
| |
in the XML output
|
|\
| |
| | |
issue #6733 invalid cite anchor id when using crossref
|
| |
| |
| |
| | |
Also test 050 was hit by the change of samlpe.bib
|
| |
| |
| |
| |
| |
| |
| | |
The crossreference possibility was not properly taken into account in bibtex conversion for other formats than LaTeX.
- doxygen.bst: use correct labels (i.e. add 'CITEREF_' in case of crossreferences to the giver name)
- cite.cpp: add the crossreferences to the citation dictionary (to overcome warning message).
- extending test 012
|
| |
| |
| |
| | |
length limitation
|
|\ \
| | |
| | |
| | | |
into mosra-extract-private-virtual
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The classic article about virtuality from Herb Sutter [1] suggests that
virtual functions are always private and public class interface is never
virtual. Until now, it was not really possible to document these
functions in Doxygen:
* Enabling EXTRACT_PRIVATE would show all internals, not just virtual
functions, which is not wanted.
* Enabling HIDE_UNDOC_MEMBERS and HIDE_UNDOC_CLASSES would effectively
disable warnings about *all* undocumented members, which is not wanted.
The usual workaround was to put the members into protected scope just
for Doxygen:
#ifdef DOXYGEN_GENERATING_OUTPUT
protected:
#else
private:
#endif
/** @brief Documented private virtual function */
virtual doStuff();
The new EXTRACT_PRIVATE_VIRTUAL option makes these visible (and able to
be linked to), but shows them *only* if they are documented.
[1] http://www.gotw.ca/publications/mill18.htm
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Test 66 gives some warning messages bout not documented entities:
.../testing/066_property_initializer.cs:4: warning: Compound Class1 is not documented.
.../testing/066_property_initializer.cs:5: warning: Member Property1 (property) of class Class1 is not documented.
.../testing/066_property_initializer.cs:6: warning: Member Property2 (property) of class Class1 is not documented.
The entities have been documented.
|
| | |
| | |
| | |
| | | |
Convert name / url based on HTML / XML conventions and don't do double conversions (XML).
|
|\ \ \
| | | |
| | | | |
Tests are unsorted
|
| | | |
| | | |
| | | |
| | | | |
When requesting all tests they are sorted in the way `glob.glob` returns them, i.e. unsorted, better, more intuitive and easier for finding problems, would be sorted.
|
|\ \ \ \
| | | | |
| | | | | |
Double defined operator in test 74
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
In test 074 the operator `&=` was identically defined twice, now corrected with const.
In XHTML this resulted in error:
`struct_foo.xhtml:204: element a: validity error : ID aa20bd44b1bb87a652ac65170ddfa1a5a already defined`
|
|/ / / |
|
| |/
|/| |
|
|/ |
|
|\
| |
| | |
Test suite and developer-facing improvements
|
| |
| |
| |
| |
| |
| | |
Tests for C++11 user-defined literals from
https://github.com/doxygen/doxygen/issues/6299 were missing, adding them
to avoid the regression re-appearing in the future.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So one can do just
./runtests.py
on Unix-like systems, instead of the unusual
python runtests.py
|
| |
| |
| |
| | |
For good measure, this one works.
|
|/
|
|
|
| |
Fails, in particular causes Doxygen to produce an empty (or truncated)
XML file but returning with a success error code.
|
| |
|
|\
| |
| |
| | |
https://github.com/mosra/doxygen into mosra-xml-namespace-members-in-file-scope
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For better consistency with the HTML output, where each file
documentation lists (and links to) all members of given namespace. This
also makes it possible to be consistent with the HTML output in case
a namespace is not documented and thus all its member detailed docs
should be put into corresponding file docs instead.
In order to be backwards compatible and avoid breaking stuff for
existing users of the XML output, this is controlled by a new
XML_NAMESPACE_MEMBERS_IN_FILE_SCOPE configuration option that defaults
to NO.
Note that this, unlike the HTML output, will put the whole detailed docs
into the file scope instead of just listing them. It's up to the user of
the XML output to deduplicate this information. It can be done for
example by comparing member ID prefixes with compound ID -- íf
different, the detailed docs are already somewhere else.
|
| | |
|
| | |
|
| | |
|