|
Boost : |
From: Thorsten Ottosen (nesotto_at_[hidden])
Date: 2005-04-23 16:19:22
"Beman Dawes" <bdawes_at_[hidden]> wrote in message
news:d4bkh6$6ht$1_at_sea.gmane.org...
|
| "Peter Dimov" <pdimov_at_[hidden]> wrote in message
| news:015b01c54770$b599c530$6501a8c0_at_pdimov2...
| > Beman Dawes wrote:
| >> The C++ standards committee's Library Working Group has proposed a
| >> schedule for library changes and extensions:
| >>
| >> * October 2005: cutoff date for C++0x major library proposals
| >> * October 2006: cutoff date for library TR2 proposals
| >> * April 2007: cutoff date for C++0x library clean-up papers
| >>
| >> The usual rule-of-thumb is that new library components go in TR2,
| >> while changes to existing components go in C++0x. The LWG will
| >> consider exceptions to the rule on a case-by-case basis.
| >
| > A threading library is an interesting specimen. Is it a C++0x or a TR2
| > thing? Given that the cutoff dates are a whole year apart...
|
| Yep, sort of an odd case. Because it is a new component, TR2 would seem the
| logical choice. But with three independent implementations (Boost,
| Dinkumware, and Metrowerks), existing practice is already considerable and
| many LWG members are already familiar with Boost.Threads. The Evolution
| Working Group is apparently also interested in pushing forward with threads
| for C++0x. Hans Boehm and others are working on core language changes to
| legitimize C++ threading and other forms of concurrent programming.
Some people in the EWG were working on threads. I belive Lawrence Crowl
was heading the group; I told to contact Kevlin Henney to let him make the
proposal;
So I don't think we need to worry about this in boost.
-Thorsten
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk