Re: [boost] Re: Non-blocking I/O

From: Matthew Austern (austern_at_[hidden])
Date: 2001-03-06 12:57:17

jk_at_[hidden] wrote:
> 
> --- In boost_at_y..., deansturtevant_at_m... wrote:
> > precedent. Anyway, in case anyone is interested, if you're using the
> > C stdin, of course Microsoft provides kbhit(). If you want to have a
> > kbhit() that works in Linux, check out the following site (which has
> > a GNU General Public License version):
> > http://src.openresources.com/debian/src/comm/HTML/S/casio_2.2.orig%
> > 20casio-2.2.orig%20boss.c.html#1182
> 
> Keyboard is not the only source of non-blocking input; another one is
> network (socket or another model), and there are many more - disk i/o
> etc. There is also need in non-blocking output.

The phrase "non-blocking I/O" seems to mean different things to different
people.

What some people are asking for here seems to be much simpler than 
non-blocking I/O in its full generality: just a non-blocking mechanism 
for detecting whether input is available.  This seems like roughly the
functionality that you get from Unix's select(2).

                        --Matt