From: David Abrahams (dave_at_[hidden])
Date: 2006-05-26 17:54:41
Beman Dawes <bdawes_at_[hidden]> writes:
> The Filesystem proposal accepted by the C++ committee's LWG for TR2
> includes components for reporting system errors from library functions
> that depend on operating system API's. There are error_code and
> system_error classes, four free functions, etc. They will go in a TR2
> header named <system_error>. Presumably for Boost it will be called
> <boost/system_error.hpp> or similar.
> Boost.Filesystem is the first Boost library to use
> <boost/system_error.hpp>. Chris Kohlhoff is planning to use it in asio,
> and has suggested improvements that I'll incorporate. Presumably the
> header will be used by other Boost libraries in the future.
> What should the roadmap be for moving this header into Boost?
> Should it be a separate library? Seems smallish for that.
> Does it need a formal review? A mini-review?
> Is it OK if I put in CVS now in boost/detail?
As long as it is an implementation detail of other libraries, it can
live in boost/detail. If it's to be a public interface, it should get
a review (mini, IMO).
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk