[boost] Re: [iostreams] non-blocking i/o : revenge of char_traits

From: Jonathan Turkanis (technews_at_[hidden])
Date: 2005-04-17 13:29:36

Jonathan Turkanis wrote:
> Hi All,

> The main technical problem is I'd have to pick values for WOULD_BLOCK
> and WWOULD_BLOCK separately for each supported standard library.

I guess I should have said "potentially" here. I'm going to try

    const int WOULD_BLOCK = (int) (EOF - 1);
    const std::wint_t WWOULD_BLOCK = (std::wint_t) (WEOF - 1);

There's also an issue with using all capital. I'd like to allow users to be able
write

    using boost::iostreams::WOULD_BLOCK

and then use two similar-looking constants EOF and WOULD_BLOCK. If more people
would start using all caps for macros, WOULD block would have a higher chance of
clashing than would_block; however, I've already had to change a bunch of
lower-case identifiers -- including "unix" and "small" -- because they were
defined as macros.

Jonathan