Re: Improving the API for read options

[Mark H Weaver]

address@hidden (Ludovic Courtès) writes:

> Mark H Weaver <address@hidden> skribis:
>
>> One problem I have with the existing API has to do with its treatment of
>> square brackets.  There are multiple things that one might want to do
>> with square brackets, but since 'square-brackets' is a boolean option,
>
> For that particular problem, I’d propose:
>
>   (set-port-read-options! PORT OPTIONS)
>
> but with OPTIONS being an list of option/value pairs, or:
>
>   (set-port-read-option! PORT OPTION VALUE)
>
> where OPTION is a symbol.
>
> Nothing fancy, but that should do the job while being reasonably
> future-proof, no?

Okay, if we limit the API to setting per-port options for now (and
leaving any unspecified options unchanged), I guess that's fine.

I'll work on it.

    Mark