Date: 2001-03-05 09:48:58
> I would like to help myself, but I'm not sure I am the best person
> design or implement such a library. If no one else will work on
> I will have to do it myself, but then I probably will not be able
> make a good enough design that it deserved to be in boost. I would
> probably just make it work for my particular application, and no
> will ever benefit from it.
It seems to me that your core point about the standard library not
addressing async programming issues is absolutely correct. The
interface you are postulating would most certainly be beneficial to
the proposed boost Socket library. Socket programming is another
place where non-blocking control flow is needed for single threaded
applications. Which brings me to a question: why not put the input
check in it's own thread?
If you are even thinking about exploring this, I suggest you take a
look at the ACE library (http://www.cs.wustl.edu/~schmidt/ACE.html).
While it is overkill for what you are doing, this library has
portable async I/O support classes.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk