|
Boost : |
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2021-05-26 17:03:30
On 5/26/21 7:46 PM, Edward Diener via Boost wrote:
> On 5/25/2021 2:00 PM, Glen Fernandes via Boost wrote:
>> On Tue, May 25, 2021 at 12:22 PM Edward Diener wrote:
>>> I have discovered a serious bug with BoostBook and nested namespaces,
>>> created an issue, but fear that no one will respond. I would like to
>>> e-mail anybody who is a maintainer for BoostBook who might be able to
>>> look at the issue and fix it, but there is no list of maintainers for
>>> Boost tools which I can find. The person who appears to have worked with
>>> BoostBook in the past, Daniel James, is no longer active with Boost so I
>>> have no idea who might be able to fix the issue.
>>
>> BoostBook has no active maintainer right now.
>
> Too bad, as the bug will not be fixed. Am I really the only person using
> the quickbook/boostbook/doxygen toolchains to document a library with
> doxygen documentation for entities in a nested namespace ? It seems so.
> I guess I will have to except the fact that the nested namespace
> entities will never be documented in the doxygen-generated reference for
> a library.
We have libraries that use QuickBook+Doxygen (I'm a maintainer of at
least two), so you're definitely not alone. At least, in Boost.Log I
have multiple nested namespaces, and I don't remember having a problem
of symbols not documented in the nested namespaces. That said, I haven't
built the docs locally for some time, so maybe something got broken...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk