port-position and get-position Shiro Kawai (19 Mar 2020 10:16 UTC)
Re: port-position and get-position Marc Nieper-Wißkirchen (19 Mar 2020 10:25 UTC)
Re: port-position and get-position Shiro Kawai (19 Mar 2020 21:07 UTC)
Re: port-position and get-position John Cowan (20 Mar 2020 02:48 UTC)
Re: port-position and get-position Shiro Kawai (20 Mar 2020 04:52 UTC)
Re: port-position and get-position John Cowan (20 Mar 2020 18:21 UTC)
Re: port-position and get-position Marc Nieper-Wißkirchen (20 Mar 2020 18:38 UTC)
Re: port-position and get-position Lassi Kortela (20 Mar 2020 18:43 UTC)
Re: port-position and get-position Shiro Kawai (20 Mar 2020 18:46 UTC)
Re: port-position and get-position Lassi Kortela (20 Mar 2020 19:17 UTC)
Re: port-position and get-position Shiro Kawai (20 Mar 2020 19:33 UTC)
Re: port-position and get-position Shiro Kawai (20 Mar 2020 19:46 UTC)
Re: port-position and get-position Marc Nieper-Wißkirchen (20 Mar 2020 07:29 UTC)
Re: port-position and get-position Shiro Kawai (20 Mar 2020 09:00 UTC)
Re: port-position and get-position Lassi Kortela (20 Mar 2020 19:12 UTC)
Re: port-position and get-position John Cowan (20 Mar 2020 19:51 UTC)
Re: port-position and get-position Marc Nieper-Wißkirchen (20 Mar 2020 20:02 UTC)

Re: port-position and get-position Lassi Kortela 20 Mar 2020 19:12 UTC

> Gauche has similar concept as port-flag (we call it port-attribute).

+1

It's useful to permit attributes that are not flags (boolean values) -
e.g. the Common Lisp reader keeps track of the current number radix.

"Property" is probably a more common word than "attribute" for things
like this but I don't know for sure.

> It is also useful to write, for example, "bytevector output port"
> similar to r7rs string output port

+1

IIRC some Schemes have one already.

> I agree that it doesn't need to be in this srfi.

OTOH it would be nice to fit all custom port stuff into one SRFI.