email@example.com ("Rolf-Thomas Happe") writes:
> stktrc writes:
>> block until there is something to read. But read-string/partial (with
>> nbytes > 0) on an (TCP) socket inport returns immediately with ""
>> (empty string, which I interpret as that no data was read). It should
>> have blocked AFAICT.
> ... except if the inport was set to non-blocking i/o (or the reader
> encountered eof). The inport state can be checked with
> (bitwise-and open/non-blocking (fdes-status inport)))
That's right. I assumed (should have checked of course) that the
socket port would not be set non-blocking by default, but it seems
like it is.