When I compile anything that includes is_abstract.hpp I get a compiler ICE with VC 7.0 since is_abstract.hpp is included by type_traits.hpp it means that a large part of boost 1.31 release candidate 2 is now uncompilable on this platform. is_abstract was known to test the limits of many platforms. It is incredible to me that this could be dropped into "release candidate # 2" without having been part of the development tree for a reasonable amount of time. When can we expect 1.31 release candidate # 3? Robert Ramey
Robert Ramey <ramey@rrsd.com> writes:
When I compile anything that includes is_abstract.hpp I get a compiler ICE with VC 7.0
since is_abstract.hpp is included by type_traits.hpp it means that a large part of boost 1.31 release candidate 2 is now uncompilable on this platform.
is_abstract was known to test the limits of many platforms. It is incredible to me that this could be dropped into "release candidate # 2" without having been part of the development tree for a reasonable amount of time.
I had the same reaction. -- Dave Abrahams Boost Consulting www.boost-consulting.com
"Robert Ramey" <ramey@rrsd.com> wrote
When I compile anything that includes is_abstract.hpp I get a compiler ICE with VC 7.0
since is_abstract.hpp is included by type_traits.hpp it means that a large part of boost 1.31 release candidate 2 is now uncompilable on this platform.
Boost.Config should be appended with new macro (BOOST_NO_SUPPORT_FOR_DR337 or better name) and is_abstract.hpp conditionally included. Current regression test results can be used to check out which compilers handle is_abstract<>. /Pavel
"Pavel Vozenilek" <pavel_vozenilek@hotmail.com> writes:
"Robert Ramey" <ramey@rrsd.com> wrote
When I compile anything that includes is_abstract.hpp I get a compiler ICE with VC 7.0
since is_abstract.hpp is included by type_traits.hpp it means that a large part of boost 1.31 release candidate 2 is now uncompilable on this platform.
Boost.Config should be appended with new macro (BOOST_NO_SUPPORT_FOR_DR337 or better name) and is_abstract.hpp conditionally included.
Current regression test results can be used to check out which compilers handle is_abstract<>.
Robert is right that this sort of change should never be made so late in a release cycle. It's especially too late in the cycle to be adding the sort of complexity you're proposing above. IMO we should take it out of the release branch. -- Dave Abrahams Boost Consulting www.boost-consulting.com
At 07:42 AM 2/1/2004, David Abrahams wrote:
"Pavel Vozenilek" <pavel_vozenilek@hotmail.com> writes:
"Robert Ramey" <ramey@rrsd.com> wrote
When I compile anything that includes is_abstract.hpp I get a compiler ICE with VC 7.0
since is_abstract.hpp is included by type_traits.hpp it means that a large part of boost 1.31 release candidate 2 is now uncompilable on this platform.
Boost.Config should be appended with new macro (BOOST_NO_SUPPORT_FOR_DR337 or better name) and is_abstract.hpp conditionally included.
Current regression test results can be used to check out which compilers handle is_abstract<>.
Robert is right that this sort of change should never be made so late in a release cycle. It's especially too late in the cycle to be adding the sort of complexity you're proposing above. IMO we should take it out of the release branch.
Way too late. John, please back it out. Thanks, --Beman
"David Abrahams" <dave@boost-consulting.com> wrote
It's especially too late in the cycle to be adding the sort of complexity you're proposing above. IMO we should take it out of the release branch.
I have no problem with it (not in 1.31). I submitted it because it got supported in GCC 3.4, not with 1.31 in mind. /Pavel
participants (5)
-
Beman Dawes -
David Abrahams -
John Maddock -
Pavel Vozenilek -
Robert Ramey