From: Andy Wingo <wingo@pobox.com>
To: No Itisnt <theseaisinhere@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: char-set-contains? and #<eof>
Date: Sun, 30 May 2010 20:08:59 +0200 [thread overview]
Message-ID: <m3hblps1ms.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTinJecu2RjnXHlOfbhUJl4B5SyGRqTzZPznd_DuS@mail.gmail.com> (No Itisnt's message of "Fri, 28 May 2010 15:52:00 -0500")
Hi,
On Fri 28 May 2010 22:52, No Itisnt <theseaisinhere@gmail.com> writes:
> R5RS specifies that character predicates should return #f,
One may interpret the language of the R5RS to permit raising an error if
the argument is not a character. Same with the R6RS. This is the tack
that Guile has taken.
For example, what would you have Guile do here:
(even? #f) => ?
(char-whitespace? 42) => ?
> The reason it bothers me is because it makes it cumbersome to deal
> with input from a port.
True; but it's just how it is, I think. The EOF object is not a
character.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-05-30 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 3:24 char-set-contains? and #<eof> No Itisnt
2010-05-28 9:21 ` Ludovic Courtès
2010-05-28 20:52 ` No Itisnt
2010-05-30 18:08 ` Andy Wingo [this message]
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=m3hblps1ms.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=theseaisinhere@gmail.com \
/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).