Re: [boost] [1.43][beta] Fix for MPL under gcc 4.5

Subject: Re: [boost] [1.43][beta] Fix for MPL under gcc 4.5
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-04-21 07:49:37

Thomas Klimpel wrote:
> Thorsten Ottosen wrote:
>
> > I in a perfect world, the GCC developers would actually test their
> > compiler on Boost before releasing it, and report back to us that we
> > have invalid code, or fix the compiler.
> >
> > What's stopping them? Or any compiler vendor for that sake?
>
> Neither msvc-10.0 nor gcc-4.5 are among the compilers that
> are tested for the release branch
> <http://www.boost.org/development/tests/release/developer/summ
> ary.html> for 1.43. So I guess it is a safe assumption that
> compatibility with msvc-10.0 or gcc-4.5 is not a release
> criteria for 1.43.

You redirected focus on Boost and the 1.43 release, which wasn't Thorsten's point.

> Making 1.44 more compatible with gcc-4.5 and MSVC-10 might be
> a good idea, but the first step in this direction should be
> to add msvc-10.0 and gcc-4.5
> to the regression tests for the release branch. And no, I
> won't donate machine time for these regression tests.

That's important, but rather late.  If the vendors test new compilers against Boost, they'd find errors in their compilers and in Boost.  Ideally, they'd fix the former before release, and it would be helpful if they reported the latter here so a coincident or immediately subsequent Boost release can include the necessary changes.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.