BOOST_FOREACH and 1.33.0
This was posted under the 'BOOST_FOREACH review results' thread but was suggested to be posted as a separate thread so others can comment on it (including the review manager and author). What do people think? Could it be pushed in to 1.33.0 or do we wait for 1.34.0 before it is added to an official release? Cheers Russell -------- Original Message -------- Pavel Vozenilek wrote:
Perhaps exception could be made - it is mature, used in apps and the documentation can be updated quickly.
It may serve as starting point for people exploring other libraries.
I would like to see it in there too. AFAICT, it doesn't require any changes to other libraries (the bcc32 addressof problem has already been patched in CVS) so its impact should be minimal to none on regression tests. I guess its would still then be up to Eric to decide if the current tests and docs are where he'd like them to be for general release after the review. Cheers Russell
On 5/5/05, Russell Hind <rh_gmane@mac.com> wrote:
What do people think? Could it be pushed in to 1.33.0 or do we wait for 1.34.0 before it is added to an official release?
If the Release Manager has no objections to its inclusion in 1.33, I vote YEA. -- Caleb Epstein caleb dot epstein at gmail dot com
Caleb Epstein wrote:
On 5/5/05, Russell Hind <rh_gmane@mac.com> wrote:
What do people think? Could it be pushed in to 1.33.0 or do we wait for 1.34.0 before it is added to an official release?
If the Release Manager has no objections to its inclusion in 1.33, I vote YEA.
1.33 has been frozen. There would have to be a pretty good reason to make an exception for FOREACH, and I haven't heard one yet. Besides, a number of issues came up in the review that I would need time to fix; namely, portability, test and doc improvements. My preference would be to wait for 1.34. People can always grab foreach.zip if they need it sooner. -- Eric Niebler Boost Consulting www.boost-consulting.com
On 5/5/05, Eric Niebler <eric@boost-consulting.com> wrote:
1.33 has been frozen. There would have to be a pretty good reason to make an exception for FOREACH, and I haven't heard one yet. Besides, a number of issues came up in the review that I would need time to fix; namely, portability, test and doc improvements. My preference would be to wait for 1.34. People can always grab foreach.zip if they need it sooner.
Being the author, we'll give you a small say in the matter as well :-) -- Caleb Epstein caleb dot epstein at gmail dot com
Russell Hind wrote:
This was posted under the 'BOOST_FOREACH review results' thread but was suggested to be posted as a separate thread so others can comment on it (including the review manager and author).
Sorry meant to add *release* manager there, but the review manager can certainly have his say also :) Cheers Russell
On May 5, 2005, at 7:51 AM, Russell Hind wrote:
This was posted under the 'BOOST_FOREACH review results' thread but was suggested to be posted as a separate thread so others can comment on it (including the review manager and author).
What do people think? Could it be pushed in to 1.33.0 or do we wait for 1.34.0 before it is added to an official release?
Wait for 1.34.0. Doug
participants (5)
-
Caleb Epstein -
Douglas Gregor -
Eric Niebler -
Jonathan Turkanis -
Russell Hind