[r6rs-discuss] No way to set current-output-port to a non-file port?
sperber at deinprogramm.de
Thu May 1 03:10:57 EDT 2008
Ryan Newton <rrnewton at gmail.com> writes:
> To clarify -- the question is why is there with-output-to-file rather
> than with-output-to-port?
For compatibility with R5RS mainly. The `current-output-port' procedure
is also there for that reason---in addition, it needs to be there so
that there's a single natively encoded port for standard output.
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
More information about the r6rs-discuss