From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: Re: srfi-14 char-set<= problem
Date: Mon, 01 Dec 2014 21:51:00 -0000 [thread overview]
Message-ID: <547CE2E5.2080602@bothner.com> (raw)
In-Reply-To: <DBAE053A-F6F4-4375-A471-D1E0C1FA14FE@theptrgroup.com>
On 11/30/2014 10:02 PM, Jamison Hope wrote:
> On Nov 27, 2014, at 12:45 PM, Seth Alves <alves@hungry.com> wrote:
>
>> (import (scheme base) (scheme write) (srfi 14))
>> (write (char-set<= (char-set #\u) (char-set #\u)))
>> (newline)
>> (write (char-set<= (char-set #\u) (char-set #\u #\a)))
>> (newline)
>>
>> This prints:
>>
>> #t
>> #f
>>
>> -seth
>
> Yup, there was a bug in the char-set<= logic. The attached patch should fix it. Per, if you would do the honors..
Checked in. Thanks.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2014-12-01 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 17:45 Seth Alves
2014-12-01 6:02 ` Jamison Hope
2014-12-01 21:51 ` Per Bothner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547CE2E5.2080602@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.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).