|
last call check
Arthur A. Gleckler
(05 May 2020 20:57 UTC)
|
|
Re: last call check
Shiro Kawai
(05 May 2020 21:26 UTC)
|
|
port positioning [was: last call check]
Per Bothner
(05 May 2020 22:22 UTC)
|
|
Re: port positioning [was: last call check]
Shiro Kawai
(05 May 2020 23:08 UTC)
|
|
Re: port positioning [was: last call check] Per Bothner (05 May 2020 23:15 UTC)
|
|
Re: port positioning [was: last call check]
Shiro Kawai
(05 May 2020 23:30 UTC)
|
|
Re: port positioning [was: last call check]
Marc Nieper-Wißkirchen
(06 May 2020 12:07 UTC)
|
|
Re: port positioning [was: last call check]
shiro.kawai@xxxxxx
(06 May 2020 12:12 UTC)
|
|
Re: port positioning [was: last call check]
Marc Nieper-Wißkirchen
(06 May 2020 12:19 UTC)
|
|
Re: port positioning [was: last call check]
John Cowan
(05 May 2020 23:53 UTC)
|
Re: port positioning [was: last call check] Per Bothner 05 May 2020 23:15 UTC
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/