| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Losslessly optimize images
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
*Total -- 536.41kb -> 410.38kb (23.5%)
/doc/extsearch_flow.png -- 20.57kb -> 7.41kb (64%)
/testing/sample.png -- 3.69kb -> 2.50kb (32.26%)
/doc/doxywizard_main.png -- 55.86kb -> 38.51kb (31.07%)
/doc/doxywizard_page1.png -- 38.72kb -> 29.24kb (24.47%)
/doc/doxywizard_page4.png -- 42.69kb -> 32.57kb (23.72%)
/doc/doxywizard_page3.png -- 49.71kb -> 37.95kb (23.66%)
/doc/doxywizard_page2.png -- 38.13kb -> 29.21kb (23.41%)
/addon/doxywizard/images/tunecolor.png -- 99.90kb -> 77.30kb (22.62%)
/doc/doxywizard_menu.png -- 57.29kb -> 45.09kb (21.28%)
/doc/doxywizard_expert.png -- 29.35kb -> 23.73kb (19.15%)
/templates/html/mag_sel.png -- 0.55kb -> 0.45kb (17.41%)
/templates/html/mag.png -- 0.51kb -> 0.44kb (14.31%)
/doc/infoflow.png -- 98.24kb -> 84.89kb (13.59%)
/templates/html/search_r.png -- 0.60kb -> 0.54kb (9.64%)
/templates/html/search_l.png -- 0.59kb -> 0.55kb (6.13%)
|
|/ /
| |
| |
| |
| |
| |
| | |
Adding attributes:
- async
- doxygen
to be able to validate doxygen generated xhtml documents
|
| |
| |
| |
| |
| |
| | |
Analogous to the `\htmlonly` also with the `\htmlinclude` command it is possible that some parts are added that cannot be inside a `<p> ... <\/p>` and thus we have to temporary close (and later reopen) the paragraph.
The option `[block]` has been added to the `\htmlinclude` command (analogous to the `\htmlonly` command).
Problem can be seen with the default doxygen test 30 (`[030_htmlinclude.dox]: test the \htmlinclude command`).
|
| |
| |
| |
| | |
Regression regarding tests
|
|\ \
| | |
| | | |
Correcting labels for citations
|
| | |
| | |
| | |
| | | |
Corrected change in test.
|
|\ \ \
| | | |
| | | | |
Extending tests with extra possibilities
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- docbook for docbook output including small test on validity (i.e. basic xml test)
- rtf for rtf output
- start_id and end_id creating the possibility to run one range of tests
-- subdirs us CREATE_SUBDIRS=YES
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Implementation of standard generator for docbook output
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Till now docbook had its own output generator, but lot of possibilities were missing (see remark about updating below), with this patch the (more than) basic implementation has been made.
Added some docbook tests to the current tests and updated documentation where necessary
Tried updating current version but too many issues remained that were generically handled in the standard generator, code is in current version behind '#if 0' construct in doxygen.cpp and name with '_v1' and in docbookgen.cp'
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
runtime.
Creating possibility to add extra doxygen configuration items to tests (e.g. QUIET=NO)
|
|\ \ \
| | | |
| | | | |
Typos found by running "codespell"
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Correct typing error in test 5
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
table of contents
- correction of compiler error (not caught on Windows)
- updated test 43 (for in page toc)
|
|\ \
| | |
| | | |
Problem with \cond in normal comment of test 015
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the \cond is also recognized in non-doxygen comment.
- As a work around the \ has been removed
- in case of e.g. pdf the enabled function is not shown as it does not have a doxygen comment
- test file output update due to change in input code.
- pre.l and commentcnv.l. better error message i.e. showing better the used condition
|
|/ / |
|
|\ \
| | |
| | | |
Create test possibilities for xhtml and pdf output
|
| | |
| | |
| | |
| | | |
Regression of default output (INPUT setting was overruled).
|
| |/
| |
| |
| |
| |
| | |
The tests in the testing directory provided possibilities to do some regression tests based on the xml output.
With the option --xhtml it is possible to see whether or not a test or set of tests is xhtml compliant.
With the option --pdf it is possible to see whether or not a test or set of tests can be build to a pdf file (per test).
|
|\ \
| | |
| | | |
Test renumbering
|
| | |
| | |
| | |
| | | |
The tests numbers 067 and 068 were used twice, test 067 has been renamed to 072 and test 068 has been renamed to 073.
|
| |/
| |
| |
| | |
The tests numbers 067 and 068 were used twice, test 067 has been renamed to 072 and test 068 has been renamed to 073.
|