Ludovic Courtès wrote:
The semantics of `get-bytevector-some', as I understand it, are similar
to that of read(2) on a blocking file descriptor:
Not really: With read(2) the caller *supplies* a buffer, and the
requested size is also provided.
it returns at least 1
byte and up to the number of requested bytes; a return value of zero
indicates end-of-file.
But for get-bytevector-some there is no "number of requested bytes".
My complaint is primarily editorial: "available data" could mean
"available without blocking" or it could mean "available in the
internal buffer".
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
