docca
docca copied to clipboard
Boost.Book XSLT C++ documentation system
A nested "using" statement which declares a type is instead listed as a member function. Example: ``` class params { public: /** A reference to an element. */ /**@{*/ struct...
When a global variable is emitted it is all on one line: ![image](https://user-images.githubusercontent.com/1503976/134364104-825335d2-5f79-4950-a4f7-949fbfe2863e.png) it would be better formatted thusly, the same as the functions: ``` constexpr bnf::lut_chars unreserved_chars; ```
It looks like when the xslt emits silver text there is a stray high-ascii character emitted: ![image](https://user-images.githubusercontent.com/1503976/134362608-42152f64-1191-4941-9da4-9ab95e52a5c6.png) Note that `` is not literal text it is actually the character hex...
This javadoc: ``` /** Insert an element This function participates in overload resolution only if `is_stringlike::value == true`. */ ``` Produces: ... `is_stringlikevalue == true` Note how the two colons...
![image](https://user-images.githubusercontent.com/1503976/132554643-b615ae33-7f7c-4986-b4db-77ed7054cd26.png)
If you group 2 friends, it works. But if you try to group another 2 friends, it stops working. ``` struct T { friend void f1a(); friend void f1b(); friend...
in consort with manually authored .qbk (Quickbook) files. This would sidestep various issues we have in attempting to faithfully generate the proper output formatting, e.g. involving getting all the right...
https://xsltng.docbook.org/
Reference to pointer should read `T*&` or `T const*&` ![image](https://user-images.githubusercontent.com/1503976/133183747-96bf4717-99bc-4424-ad4d-6746ad4903fc.png)
This ``` @par paragraph1 @par paragraph2 ``` produces: ![image](https://user-images.githubusercontent.com/1503976/132994170-5a955066-b968-4de1-b84f-9e0dd4739fd7.png) If we could use `@par` without a title as a workaround to denote a paragraph break, in case we can't get...