[R6RS] Timeline for R6RS SRFIs
Thu Jun 9 01:32:36 EDT 2005
"Manuel Serrano" <Manuel.Serrano at sophia.inria.fr> writes:
> On Wed, 08 Jun 2005 14:40:17 +0200
> Michael Sperber <sperber at informatik.uni-tuebingen.de> wrote:
>> I assume you mean OPEN-INPUT-PROCEDURE, as documented in the Bigloo
> No, this is not what I have in mind. [...]
> Now let me describe briefly what I had in mind. A port is a data structure
> which contains a bunch of fields which are more or less implementation
> - an actual file descriptor
> - a name
> - a buffer
> - a buffer size
> - ...
> Amongst these fields three are functions:
> - sysread
> - syseof
> - sysclose
> Each of these fields is used to implement the eponym system functionality.
> When the port's buffer has to be filled, the sysread function is invoked.
> When a port has be to closed, the sysclose function is invoked, etc.
> These functions can accept the port as argument or the buffer. It's not
> This model scales up (as I mentioned it enables user applications to
> define new port types) and it is efficient. If you think it's not,
> let's try to run some benchmarks in order to have a better understanding
> of what we are pretending.
No, I don't---this sounds basically equivalent to the Primitive I/O
layer in SRFI 68. Sorry for the misunderstanding---I think we agree
on this count.
Cheers =8-} Mike
Friede, V?lkerverst?ndigung und ?berhaupt blabla
More information about the R6RS