From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Improving the API for read options
Date: Sun, 11 Nov 2012 02:56:49 -0500 [thread overview]
Message-ID: <87sj8g8tdq.fsf@tines.lan> (raw)
In-Reply-To: <87zk2usghj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 06 Nov 2012 20:01:28 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> 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
next prev parent reply other threads:[~2012-11-11 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 23:59 [PATCH] Make `get-datum' conform more closely to R6RS semantics Andreas Rottmann
2012-11-05 5:07 ` Mark H Weaver
2012-11-05 17:52 ` Ludovic Courtès
2012-11-06 7:36 ` Improving the API for read options Mark H Weaver
2012-11-06 19:01 ` Ludovic Courtès
2012-11-11 7:56 ` Mark H Weaver [this message]
2012-11-06 19:55 ` [PATCH] Make `get-datum' conform more closely to R6RS semantics Andreas Rottmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj8g8tdq.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).