Date: 2001-03-15 13:56:13
--- In boost_at_y..., "Peter Dimov" <pdimov_at_m...> wrote:
> From: <williamkempf_at_h...>
> > You miss the problem here. Yes, I could expose an errno that
> > implementation specific here. But it's pointless in a portable
> > sense, since it IS implementation specific. Client code can not
> > use of the errno in a portable manner.
> It can call std::strerror with the error code as an argument. If it
> from errno, then it must work with std::strerror, at least this is
When we say "errno" here we're not necessarily talking about the
global std::errno variable. We just mean an error code returned from
an API. Often these error codes are platform specific and
std::strerror isn't going to help us translate them.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk