This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Updating <condition_variable>
- From: Chris Fairles <chris dot fairles at gmail dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 16 Dec 2009 14:14:15 -0500
- Subject: Re: Updating <condition_variable>
- References: <4B28C8A4.3030008@oracle.com>
No real plans to begin working on condition_variable_any (at least, I
haven't made any progress, nor will I have time to commit until the
new year). I haven't reviewed n3000 recently either.
On a somewhat related note, I do have an old <mutex> fix however for
the generic try_lock (removing the tuple usage, on failure it should
only unlock those that it successfully locked). Been trying to get my
dev. environment back up to snuff to run regression tests and will
submit as soon as they pass (very soon).
Chris
On Wed, Dec 16, 2009 at 6:46 AM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi,
>
> in preparation for 4.5.0, rather close now, I think it could be nice if
> we could make some progress on <condition_variable>, thus updating the
> interfaces to the current WP n3000 (in particulat, wrt DR 857),
> finishing the implementation of the condition_variable_any members, etc.
> I can work on this, but it would be of course nice if Chris could
> follow-up to his own work... Any plan, Chris?
>
> Thanks,
> Paolo.
>
> //////////
>