From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: char-set-contains? and #<eof>
Date: Fri, 28 May 2010 11:21:34 +0200 [thread overview]
Message-ID: <87eigwidpd.fsf@gnu.org> (raw)
In-Reply-To: AANLkTikpekY58j-WBWs-nimGYeZyRufmkuz-79R50b9I@mail.gmail.com
Hi,
No Itisnt <theseaisinhere@gmail.com> writes:
> It's getting pretty annoying that char-set-contains? rejects #<eof>.
It makes sense to me given that SRFI-14 (informally) defines the second
argument as being a character (and #<eof> is not a character):
http://srfi.schemers.org/srfi-14/srfi-14.html#char-set-contains-p
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-05-28 9:21 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 [this message]
2010-05-28 20:52 ` No Itisnt
2010-05-30 18:08 ` Andy Wingo
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=87eigwidpd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).