Re: [boost] Boost.TR1: A first cut.

From: Beman Dawes (bdawes_at_[hidden])
Date: 2005-01-23 20:14:57

At 07:21 PM 1/23/2005, Jeff Garland wrote:

 >On Fri, 21 Jan 2005 16:42:52 -0000, John Maddock wrote
 >> I've just uploaded to the new sandbox-vault a first cut of a
 >> Boost.TR1 library, currently it only handles chapter 2 of the TR -
 >
 >Since no one is answering, I'll take a shot...
 >
 >> so basically only shared_ptr is usable at present, but now that I've
 >> got the basic framework sorted I should be able to wiz through the
 >> rest of the TR in fairly short order.
 >>
 >> The zip is at:
 >>
 >http://boost-sandbox.sourceforge.net/vault/index.php?&direction=0&order=&dir
 >ectory=tr1
 >> And the docs are online at:
 >> http://freespace.virgin.net/boost.regex/tr1/tr1.html
 >
 >I browsed these -- they look good.
 >
 >> At this stage I'm just trying to get some feedback on:
 >>
 >> 1) Is this worth doing?
 >
 >Seems like it will be worthwhile if
 >1) it is done ahead of vendor tr1 packages
 >2) it is better in some way then vendor packages
 >
 >I would imagine in the future people will prefer to use the tr1 bundled
 >with
 >their std library of choice unless one of the conditions above hold true.
 >Also, it won't be a complete tr1 without the hash stuff, so that will 
need
 >to be noted (I'm assuming that wouldn't get into boost in time).
 >Interestingly, there might be an argument for a boost distribution with
 >the tr1 libraries
 >removed from the boost package since they would be 'obsolete' -- argument
 >being to avoid confusion for developers on project xyz we want to remove
 >these.

My prediction is that it will be four to six years before all the compilers 
boost users care about ship with the full tr1 in the box. So during that 
time period it will be a real service to users if we provide major portions 
of the TR. John's approach looks like a good way to do that, although so 
far I've only read the docs but not actually tried it in practice.

--Beman