docca
docca copied to clipboard
boostorg
Boost.Book XSLT C++ documentation system
A square bracket wrecks the works
For example: ``` class T { protected: T() = default; public: T(T const&) = delete; T& operator=(T const&) = delete; }; ``` This will generate the wrong link targets
When template parameters are specified using `@tparam`, the heading "Template Parameters" should be output above the list as it is shown fo parameters using `@param`.
Given free function declarations: ``` /// X int& foo(); /// Y int const& foo(); ``` The overloads section will show only `X`. However, if these functions are class member functions,...
Static class data and member functions should be in their own sections. This is a simple change and already working in Beast's fork of the xsl.
Any changes to the "id" of a class member within `make_id` with a leading underscore breaks the link from within the class (though the member page is still generated, appears...
`@return A parser for a message with the specified @b Body type.` Body should be in bold but its not.
For example: [class](http://vinniefalco.github.io/docca/beast/ref/beast__basic_streambuf.html) [method](http://vinniefalco.github.io/docca/beast/ref/beast__basic_streambuf/allocator_type.html) A workaround is to manually specify an explicit heading level, e.g. `[h3 Synopsis]` This most likely is caused when symbols are at different section nesting depth...
We need a way for projects using docca to provide information about specific types in the project that have associated docs. The project authors should be able to provide an...
Regardless of input order, we want section predictably ordered in output.