On Mon, Aug 14, 2017 at 8:31 PM, Robert Ramey via Boost wrote:
On 8/14/17 10:37 AM, John Maddock via Boost wrote:
BTW is there any reason to continue using the Boostbook customisation layer? Is anyone actually using it? I'm fairly sure quickbook doesn't, and it would sure simplify the build process to leave out one level of XSL transformation. Sadly we would need an XSL expert to sort that mess out I suspect :(
I think there's a little more to this:
a) There are special tags like class, struct, etc. etc. Which permit tagging for different aspects of C++ syntax. Somehow I doubt anyone is using this stuff. It would be pain to edit it and it would presume that every class,struct etc would have the same documentation structure which might be inconvenient. Also the documentation for this is reference and doesn't give much in the way of sample output etc. Upshot I'm doubtful that anyone is using it.
Is the Boost.Array documentation not using this? https://github.com/boostorg/array/tree/develop/doc Glen