Re: Nonblocking get-bytevector-n bug?

[Ludovic Courtès]

address@hidden (Taylan Ulrich "Bayırlı/Kammer") skribis:

> address@hidden (Taylan Ulrich "Bayırlı/Kammer") writes:
>
>> address@hidden (Ludovic Courtès) writes:
>>
>>> Not sure what R7 does here.
>>
>> R7RS section 6.13.2 Input, page 58, defines:
>>
>>     (read-bytevector! bytevector [port [start [end]]])
>>
>>     Reads the next END - START bytes, or as many as are available before
>>     the end of file, from the binary input PORT into BYTEVECTOR in
>>     left-to-right order beginning at the START position.  If END is not
>>     supplied, reads until the end of BYTEVECTOR has been reached.  If
>>     START is not supplied, reads beginning at position 0.  Returns the
>>     number of bytes read.  If no bytes are available, an end-of-file
>>     object is returned.
>>
>> Maybe the r7rs-wip branch has an implementation of it.
>
> Eh, never mind, this seems to imply blocking ("as many as are available
> before the end of file").

Yes, but only “until the end of BYTEVECTOR has been reached.”

Ludo’.