> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Sunday, October 18, 2020 8:04 AM
>
> Is SRFI 205 intended to cover terminals over serial port, giving the
> Scheme programmer control over transmission speed, parity bits and such?

Not exactly, if by terminals you mean a real physical or virtual terminal
at the other end of the serial line, that falls under retrocomputing.

Complete support of serial ports for embedded and the like programming is
officially in its remit.  In part this comes from the best implementation
strategy for doing that, create your own programmatic stty, which John
didn't want to require in SRFI 170.

But once you do that, the with-* and without-echo procedures become trivial
or nearly so in terms of POSIX (to do timeouts and minimum number of
characters to read, stty VTIME and VMIN, you have to get into an array
in a C struct, that isn't as trivial to wrap as a struct's simple members).

> We should think up the use cases and arrive at a good factoring of SRFIs
> to give Scheme coders a set of interfaces that are easy to use safely.

All part of the plan, but delayed for now due to Real Life issues, which
are hopefully getting resolved soon.

- Harold