David Abrahams wrote:
Might be a good idea. I think I'd like to continue to support vc6 at least on the 1.31.x branch, particularly because last-minute changes in the graph library broke Boost.Python on vc6 for 1.31.0
What would we do about Borland, which is in some ways more broken than vc6? They don't ship a compiler I wouldn't consider broken.
Well, I only use bcc32 and for now, I'm happy to stick with 1.30.2. I'll back port any new features I need myself (mainly from filesystem/thread if any attractive features come in) and I may move to 1.31.0 but I've run into other problems using this at the moment so I can only speak for myself about bcc32, but as spirit has already dropped support for bcc32 in 1.31.0 (spirit-1.8 IIRC) then it means boost can't be used 'out-of-the-box' anyway, and requires still having 1.30.2 around anyway. But the new compiler is in preview (bccx 6.0) and already works with quite a bit of boost (thanks to John Maddock) and there hasn't been a word yet, but it has been in preview for about 5 months now and the talk was of the next version of CBX (hopefully with the final product int) due 2-3 quarter this year, so we may be able to get Borland support back in the not too distant future (without all the work-arounds currently needed). Thanks Russell