[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Nonblocking get-bytevector-n bug?
|
From: |
Marko Rauhamaa |
|
Subject: |
Re: Nonblocking get-bytevector-n bug? |
|
Date: |
Wed, 09 Dec 2015 00:02:53 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Marko Rauhamaa <address@hidden>:
> It seems to me whoever wrote the spec wasn't thinking of nonblocking
> ports at all. Are nonblocking ports recognized by RnRS?
Took a quick glance at the R6RS spec. It would appear nonblocking ports
are *not* mentioned or thought of in it.
Thus, *any* nonblocking behavior would be an extension to R6RS, and
Guile can do whatever it wishes.
Marko
- Re: Nonblocking get-bytevector-n bug?, (continued)
Re: Nonblocking get-bytevector-n bug?, Marko Rauhamaa, 2015/12/07
Re: Nonblocking get-bytevector-n bug?, Amirouche Boubekki, 2015/12/07
Re: Nonblocking get-bytevector-n bug?, Mark H Weaver, 2015/12/08