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
In light of the recent security vulnerability on using localhost + port,
I've been using socket files for live hacking. Unfortunately, these
socket files stay around after closing guile, which means this can happen:
$ guile --listen=/tmp/guile-socket
scheme@(guile-user)> ,q
$ guile --listen
I noticed that 00-repl-server.test had failed on some of the debian
buildds like this:
Running 00-initial-env.test
Running 00-repl-server.test
FAIL: 00-repl-server.test: repl-server: simple expression - arguments:
(expected-value "scheme@(repl-server)> $1 = 42\n" actual-value "$1 = 42\n")
merge 24819 24769
thanks
Rob Browning writes:
> I noticed that 00-repl-server.test had failed on some of the debian
> buildds like this:
>
> Running 00-initial-env.test
> Running 00-repl-server.test
> FAIL: 00-repl-server.test: repl-server: simple expression - arguments:
> (expected-value
