Boost logo

Boost :

Subject: [boost] Standard library Technical Report 2 proposals for Boost libraries
From: Beman Dawes (bdawes_at_[hidden])
Date: 2011-11-14 14:14:15


The C++ committee hasn't decided whether to do a TR2 or to move
directly on to the next standard. Either way, there will be a call for
library proposals, but the details will be up in the air at least
until the next meeting, which will be in Kona, Hawaii, in February.
For the moment, the term "TR2" is being used as a surrogate for moving
the standard library forward regardless of exact details.

In discussions, library working group (LWG) members have made it clear
they want a filesystem library based on Boost.Filesystem, and a
networking library based on Boost Asio. Individual members of the
committee have voiced interest in other Boost libraries, large and
small.

If you are a Boost developer (or user), and there is a Boost library
you would like to see proposed for TR2, now is a good time to start
thinking about writing a preliminary proposal to the committee. The
point of such a proposal is to gauge interest before putting in a lot
of work on a full-blown proposal only to find the LWG isn't
interested.

See http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1810.html
for the original TR2 call for proposals. While the details will
change, it is still a reasonable introduction to what is required. A
preliminary proposal would just say "To be supplied" for the "Proposed
Text for the Standard" section.

It is very helpful to do at least the initial presentation of such a
proposal in person. That said, John Maddock and Peter Dimov had many
proposals accepted for TR1 without ever attending a standards
committee meeting. If you don't plan to present a proposal in person,
the best bet is to ask someone who is familiar with the library to
present it.

Feel free to contact me publicly or privately with questions about
proposals or information about attending committee meetings,

--Beman


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk