On 5/5/20 4:08 PM, Shiro Kawai wrote:
> One not-so-obvious consequence is that textual input/output port requires get-position/set-position!
> even the user won't call port-position/set-port-position!, if we adopt that peek-char doesn't move the
> position.  It's because write-char followed by peek-char must overwrite the peeked position, which
> means the custom port needs to move the position back before calling write!.

Is there any valid use-case for textual input/output ports?  Do they make any sense?  I doubt it,
certainly not enough to be in a Scheme standard.
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/