[TR1] Where is the TR1 library?
Google found me a 12 October 2005 posting by Beman Dawes to this newsgroup stating that John Maddock's TR1 library has been accepted by Boost. But if I search for TR1 at http://boost.org/libs/libraries.htm, I don't find the library. Searching more generally yields lots of hits at www.boost.org/regression-logs/ (e.g., http://www.boost.org/regression-logs/cs-win32_metacomm/doc/html/boost_tr1.ht...), and this suggests that just because a library has been accepted by Boost doesn't mean it will show up in the list at http://boost.org/libs/libraries.htm. Can somebody please explain to me what are probably the basics of what it means to be "in" Boost, how that interacts with the list of Boost libraries at boost.org, and what the significance of the regression-logs directory is? If this is explained somewhere at Boost, just point me to the page. Thanks, Scott
On Sun, 12 Feb 2006 20:37:32 -0800, Scott Meyers wrote
Google found me a 12 October 2005 posting by Beman Dawes to this newsgroup stating that John Maddock's TR1 library has been accepted by Boost. But if I search for TR1 at http://boost.org/libs/libraries.htm, I don't find the library. Searching more generally yields lots of hits at www.boost.org/regression-logs/ (e.g., http://www.boost.org/regression-logs/cs- win32_metacomm/doc/html/boost_tr1.html), and this suggests that just because a library has been accepted by Boost doesn't mean it will show up in the list at http://boost.org/libs/libraries.htm. Can somebody please explain to me what are probably the basics of what it means to be "in" Boost, how that interacts with the list of Boost libraries at boost.org, and what the significance of the regression- logs directory is?
It just means that the TR1 library isn't in the current boost release (1.33.1) that you can download. It's been accepted and is in the mainline repository -- hence it is being regression tested and prepared for the next release. So if you want to play with it you will need to get the latest version of CVS (see instructions here http://boost.org/more/getting_started.html#CVS) The best way to see the state of the libraries is on the the review schedule page: http://boost.org/more/formal_review_schedule.html HTH, Jeff
It just means that the TR1 library isn't in the current boost release (1.33.1) that you can download. It's been accepted and is in the mainline repository -- hence it is being regression tested and prepared for the next release. So if you want to play with it you will need to get the latest version of CVS (see instructions here http://boost.org/more/getting_started.html#CVS)
Thanks for the quick clarification. Scott
Jeff Garland wrote:
On Sun, 12 Feb 2006 20:37:32 -0800, Scott Meyers wrote
this suggests that just because a library has been accepted by Boost doesn't mean it will show up in the list at http://boost.org/libs/libraries.htm. Can somebody please explain to me what are probably the basics of what it means to be "in" Boost >
It just means that the TR1 library isn't in the current boost release (1.33.1) that you can download. It's been accepted and is in the mainline repository -- hence it is being regression tested and prepared for the next release.
Now that I think about it some more, I'm confused. My understanding is that a library can be in one of the following states: - In the current distribution. - Accepted but not yet in the current distribution (includes provisionally accepted). - In the process of being reviewed. But I also hear a lot about libraries being in the Boost sandbox, and I don't really know what that means. Is this explained somewhere? If not, can somebody give me an overview of the different ways in which a library can be associated with Boost? In the past, my relationship with Boost was simple: from time to time, I downloaded the current release and went my merry way. Now I understand that the current release doesn't cover everything in Boost, and I'd like to better understand the other relationships that a library can have with Boost. Thanks, Scott
Scott Meyers
Jeff Garland wrote:
On Sun, 12 Feb 2006 20:37:32 -0800, Scott Meyers wrote
this suggests that just because a library has been accepted by Boost doesn't mean it will show up in the list at http://boost.org/libs/libraries.htm. Can somebody please explain to me what are probably the basics of what it means to be "in" Boost >
It just means that the TR1 library isn't in the current boost release (1.33.1) that you can download. It's been accepted and is in the mainline repository -- hence it is being regression tested and prepared for the next release.
Now that I think about it some more, I'm confused. My understanding is that a library can be in one of the following states: - In the current distribution. - Accepted but not yet in the current distribution (includes provisionally accepted). - In the process of being reviewed.
There's also: - in the review queue - in a stable state but with no review requested (yet) - in development Only the first one of those last three has any formal status.
But I also hear a lot about libraries being in the Boost sandbox, and I don't really know what that means. Is this explained somewhere?
It's just a repository for code in one of the last 2 states.
If not, can somebody give me an overview of the different ways in which a library can be associated with Boost?
Only an accepted library is a Boost library, but people develop code all the time with the intention of making a Boost library.
In the past, my relationship with Boost was simple: from time to time, I downloaded the current release and went my merry way. Now I understand that the current release doesn't cover everything in Boost, and I'd like to better understand the other relationships that a library can have with Boost.
I'll be covering all this in my SD West talk. Unfortunately, as you know, our talks overlap ;-) -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
There's also: - in the review queue - in a stable state but with no review requested (yet) - in development
Only the first one of those last three has any formal status.
But I also hear a lot about libraries being in the Boost sandbox, and I don't really know what that means. Is this explained somewhere?
It's just a repository for code in one of the last 2 states.
So people developing code with an eye towards submission to Boost may choose to do their development in the sandbox, but this is not required, right? Have most submissions spent time in the sandbox, or is it equally common for somebody to submit something they'd been working on their own completely independent of Boost?
I'll be covering all this in my SD West talk. Unfortunately, as you know, our talks overlap ;-)
Which I truly regret, but that notwithstanding, is this information available at Boost somewhere? If not, I think it would be helpful for more people than just me. Thanks, Scott
Scott Meyers
So people developing code with an eye towards submission to Boost may choose to do their development in the sandbox, but this is not required, right?
Correct.
Have most submissions spent time in the sandbox, or is it equally common for somebody to submit something they'd been working on their own completely independent of Boost?
I'm not really sure of the statistics, sorry. You can browse the sandbox over the web to get an idea.
I'll be covering all this in my SD West talk. Unfortunately, as you know, our talks overlap ;-)
Which I truly regret, but that notwithstanding, is this information available at Boost somewhere? If not, I think it would be helpful for more people than just me.
Agreed; we're reworking the site and I'll try to get it in. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (3)
-
David Abrahams -
Jeff Garland -
Scott Meyers