|
Boost : |
Subject: Re: [boost] Proposed SG14 <system_error2> ready for feedback
From: Andrzej Krzemienski (akrzemi1_at_[hidden])
Date: 2018-03-01 16:05:42
2018-02-28 23:10 GMT+01:00 Niall Douglas via Boost <boost_at_[hidden]>:
> Back after the Outcome discussion died down, I started a thread
> discussing making breaking changes to Boost.System to test the
> feasibility of fixing some of the unfortunate design choices now
> apparent through hindsight in `<system_error>`. I won one argument -
> constexprification - the others I lost. I said at the time that I'd go
> off and make a better mousetrap i.e. a proposed `<system_error2>`.
>
> That proposed `<system_error2>` is now ready for feedback:
>
> Single file include:
> https://github.com/ned14/status-code/raw/develop/
> single-header/system_error2.hpp
>
> Github: https://github.com/ned14/status-code
>
> Docs: https://ned14.github.io/status-code/
The github readme at https://github.com/ned14/status-code gives a clear
description how I can make use of POSIX and Windows-standard error codes.
Could we have similar short and clear examples illustrating how one can:
1. Create a custom error_category (or equivalent thing)
2. Use parametrized statuc_code
3. Use type-erased status_code
Regards,
&rzej;
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk