[Prev][Next][Index][Thread]

# Re: read() subtlety

- Date: Thu, 12 Sep 1996 11:47:01 PDT
- From:
- cc: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>, MOO-cows list <MOO-Cows.parc@xerox.com>
- In-Reply-to: "Christopher Unkel's message of \"Thu, 12 Sep 1996 09:33:26 PDT\" <Pine.SUN.3.95.960912122619.20708A-100000@ren.us.itd.umich.edu> "

    Christopher Unkel writes:
    > If there is input available, read() returns immediately without
    > suspending.

    This is not true; if the non-blocking flag is false or absent, then the read()
    function *always* suspends the calling task; this is clear from the bf_read()
    code in execute.c.  I don't have an explanation for the problem Gustavo is
    seeing.

    	Pavel

References:

- Re: read() subtlety

- From: Christopher Unkel <cunkel@us.itd.umich.edu>

- Prev: Re: read() subtlety
- Next: resolving player request addresses
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index