[core] scoped enum authoring
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. BTW, there is no deprecation for the Beman version, there are just different advantages and liabilities. I suspect that the same is applied to the other component of the Boost.Core module Thanks for working on this. Vicente
On Thu, Jun 5, 2014 at 11:03 AM, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> 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.
On 5 June 2014 08:15, Andrey Semashev <andrey.semashev@gmail.com> wrote:
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).
Specifying the author is a docbook feature, and can't be done for sections, so to have different authors for different parts of the documentation you need to make those sections articles, or chapters, or something along those lines. Which isn't strictly valid inside a 'library' or 'chapter', so I'm not sure if it can work as part of the combined documentation. You could change the documentation to be a 'book', and then have chapters for each submodule (quickbook 1.6 respects docinfo in included files).
Le 05/06/14 09:15, Andrey Semashev a écrit :
On Thu, Jun 5, 2014 at 11:03 AM, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> 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.
Hi, I was not aware if this change. Andrey I don't know if you or Anthony did the changes, please, be free to add you or him as author also. Could I have write access to this component to update the documentation and add some tests? Thanks, Vicente
On Thursday 05 June 2014 23:29:09 Vicente J. Botet Escriba wrote:
Le 05/06/14 09:15, Andrey Semashev a écrit :
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.
Hi,
I was not aware if this change. Andrey I don't know if you or Anthony did the changes, please, be free to add you or him as author also.
This was already done by Anthony before I moved the code. I added him to authors and Acknowledgements.
On Thu, Jun 5, 2014 at 12:03 AM, Vicente J. Botet Escriba wrote:
I would appreciate if both Beman and I are added as authors.
[snip]
I suspect that the same is applied to the other component of the Boost.Core module
It's nothing fancy, but here goes: http://boostorg.github.io/core I added a similar Authors section to every page. And simplified the indexing a little (the table was a little redundant for most components and would only become a maintenance headache; naming each component by headers was also less useful for components which include multiple headers). Glen
participants (5)
-
Andrey Semashev -
Daniel James -
Glen Fernandes -
Peter Dimov -
Vicente J. Botet Escriba