Do we need to do anything special? Boost policy is not to require compatibility with non-conforming compilers and testing markup can be used to indicate which libraries should not be tested with specific compilers. Maybe the only thing necessary is to make this information a little more visible through the web site so we have a table indicating which libraries support which compilers. (I'm sure its already in there somewhere - it would just have to be made a little more prominent) If we try to do anything else like agree which should be supported and which not we'll end up in interminable round of discussions which will never be totally satisfactory. Already we have spirit which is not supported on some platforms. This works well. Robert Ramey Paul A Bristow wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Victor A. Wagner Jr. Sent: 05 December 2005 01:02 To: boost@lists.boost.org; boost@lists.boost.org Subject: Re: [boost] Permanently retire VC++ 6? (was:Re:Math/Quaternions compile problem in VC++6)
and I'm all for retiring vc++6.0 support from boost (I've argued this before).
This is long overdue and now that we have a reasonably compliant MSVC compiler that works on Windows 2000 up I can't see any excuse for not dropping support. Things that this work will still work, but if not - tough. (I am not proposing ripping out all the #ifdefs relating the MSVC 6, despite the improvement in readability that might result).
Should we have a straw poll of the lurkers - so that diehards can have their say - and then make a decision?
Paul