| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Adding the xml:lang attribute for XNL and Docbook output
Interesting links:
- language codes (different from country codes!): https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
- example for xml.xsd: http://www.java2s.com/Code/XML/XML-Schema/importanotherXMLschema.htm
|
| |
|
|
|
|
| |
in the XML output
|
|
|
|
| |
The tests numbers 067 and 068 were used twice, test 067 has been renamed to 072 and test 068 has been renamed to 073.
|
|\ |
|
|
|
|
|
|
|
|
|
|
|
| |
* testing/067_link_varargs.cpp: new file, @link regression test for
variadic function arguments '...'
* testing/067/067__link__varargs_8cpp.xml: new file, expected @link
regression test result for variadic function arguments '...'
* testing/068_ref_varargs.cpp: new file, @ref regression test for
variadic function arguments '...'
* testing/068/068__ref__varargs_8cpp.xml: new file, expected @ref
regression test result for variadic function arguments '...'
|
|
|
|
|
|
|
| |
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.
|
|
The <type> element (used for function return type and variable type) is
now reused also for underlying enum type.
C++03-style enum types that don't have the underlying type specified
have the <type> tag as well, but empty to indicate that the underlying
type is unspecified.
Added a new test case for this.
|