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

# Re: read() subtlety

- Date: Thu, 12 Sep 1996 07:15:06 PDT
- From:
- cc: MOO-cows list <MOO-Cows.parc@xerox.com>
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- References: <v03007802ae5d60addd8b@[132.76.55.49]>

    Gustavo Glusman wrote:

    > This seems to imply that read() *always* suspends, even if input is
    > already available thorugh that connection. But the behaviour seems to
    > suggest that some of the read() calls are not suspending? How else
    > could it run out of ticks on line 10?

    I recall reading...either in the changelog, or in the programmer's manual
    itself, that read() was modified in 1.8.0 to not suspend if there is input
    pending in the connection's network buffer.

    But I'm not sure...?

References:

- read() subtlety

- From: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>

- Prev: read() subtlety
- Next: Re: read() subtlety
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index