Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of Farid_Zaripov@epam.com
 designates 217.21.63.3 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: status of Boost with stdcxx
Date: Fri, 25 May 2007 10:20:43 +0300
Message-ID: <7BDB2168BEAEF14C98F1901FD2DE6438869058@epmsa009.minsk.epam.com>
In-Reply-To: <46547B21.3050304@roguewave.com>
Thread-Topic: status of Boost with stdcxx
Thread-Index: AcedYJgEQk8r40vHRo+VdyKL7vawVgBPD0Jg
References: <46534417.2010609@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE6438868D3D@epmsa009.minsk.epam.com>
 <46547B21.3050304@roguewave.com>
From: "Farid Zaripov" <Farid_Zaripov@epam.com>
To: <stdcxx-dev@incubator.apache.org>

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]=20
> Sent: Wednesday, May 23, 2007 8:34 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: status of Boost with stdcxx
>=20
> Farid Zaripov wrote:
> >> -----Original Message-----
> >> From: Martin Sebor [mailto:sebor@roguewave.com]
> >> Sent: Tuesday, May 22, 2007 10:27 PM
> >> To: stdcxx-dev@incubator.apache.org
> >> Subject: status of Boost with stdcxx
> >>
> But they do plan to fix them for the next release, right?
  Yes, sure.

> I want to make sure there's no dispute about the issues you=20
> filed and that they will eventually get addressed.

> > So, we need to make the new scripts...
>=20
> So the .jam files you put together don't work for the 1.34.0=20
> release of Boost?

  Right.

> If that's correct, let's rewrite them to=20
> conform to version 2 so that people have an easy way of using=20
> the latest Boost libraries with stdcxx. Once you're done we=20
> should publish the scripts on our site for people to download=20
> until we get Boost to accept and ship them in the next=20
> release of their libraries.

  Ok.

> >> Finally, are there any
> >> outstanding issues on our end that we need to address in order for=20
> >> stdcxx to be fully usable with the Boost libraries?
> >   I'll try to build stdcxx with last release of the boost=20
> to see what=20
> > left to fix.
>=20
> Okay. It would be good to keep track of all these issues in=20
> some central location. How about creating a Jira task for=20
> this whole project ("using Boost with stdcxx") and a subtask=20
> for each problem you (and our users are likely to) run into?

  Ok, I'll make the Jira task soon.

Farid.