[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24816: Bug in (rnrs io ports) procedure open-string-output-port
From: |
Freja Nordsiek |
Subject: |
bug#24816: Bug in (rnrs io ports) procedure open-string-output-port |
Date: |
Sat, 29 Oct 2016 17:29:09 +0700 |
The "open-string-output-port" procedure in (rnrs io ports) returns two
values, a string port and a thunk that returns a string of the
characters written to the port so far. In the R6RS standard documents,
the reading procedure is destructive, in that it clears all the
characters written to the port so far (though, it does not close it,
so it can still be used). However, in Guile 2.1.4, the characters are
not cleared and so running the thunk again immediately afterwards will
produce the same output, which is a bug.
This can be tested running the following script
(import (rnrs base (6))
(rnrs io ports (6))
(rnrs io simple (6)))
(let-values (((p get-output) (open-string-output-port)))
(display "hello" p)
(flush-output-port p)
(let ((out-first (get-output)))
(let ((out-second (get-output)))
(display (string-append "Follows R6RS: "
(if (string=? out-first out-second)
"no"
"yes")))
(newline)
(display (string-append "out-first: " out-first))
(newline)
(display (string-append "out-second: " out-second))
(newline))))
which produces the following output in guile
Follows R6RS: no
out-first: hello
out-second: hello
when it should output
Follows R6RS: yes
out-first: hello
out-second:
instead.
Freja Nordsiek
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#24816: Bug in (rnrs io ports) procedure open-string-output-port,
Freja Nordsiek <=