$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [core] scoped enum authoring
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-06-05 03:15:28
On Thu, Jun 5, 2014 at 11:03 AM, Vicente J. Botet Escriba
<vicente.botet_at_[hidden]> wrote:
> Hi Andrey.
>
> In the Boost.Core documentation I see:
>
> "Thanks to Andrey Semashev for pointing out that emulation through a
> namespace could not be used within classes.
>
> Helpful comments and suggestions were also made by Kjell Elster,
> Phil Endecott, Joel Falcou, Mathias Gaunard, Felipe Magno de
> Almeida, Matt Calabrese, Vicente Botet, and Daniel James."
>
> The authors of this file are Beman (for the class based version) and me (for
> the namespace based). As the documentation has been mainly extracted from
> the file
> I would appreciate if both Beman and I are added as authors.
I just replicated the acknowledgements that were present as a comment
in the original header (except I moved myself from the technical
description to this dedicated section).
Will it be ok if I add you and Beman in the beginning of the
Acknowledgements section? I don't know how to set the authors just for
this page (i.e. those listed in the QuickBook header and displayed in
the bottom right of the generated html).
> BTW, there is no deprecation for the Beman version, there are just different
> advantages and liabilities.
You mean BOOST_SCOPED_ENUM_START/BOOST_SCOPED_ENUM_END macros? In the
implementation they were (and are) equivalent to
BOOST_SCOPED_ENUM_DECLARE_BEGIN/BOOST_SCOPED_ENUM_DECLARE_END. There
seems to have been the difference at some point but no more. Given
that the latter offer more flexibility, I deprecated the others.
> I suspect that the same is applied to the other component of the Boost.Core
> module
Yes, we need to specify the authors of the components in the docs somehow.