From: Mark H Weaver <mhw@netris.org>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: Two r6rs bugs
Date: Sun, 25 Nov 2012 10:58:08 -0500 [thread overview]
Message-ID: <87d2z11xpr.fsf@tines.lan> (raw)
In-Reply-To: <878v9pdfve.fsf@Kagami.home> (Ian Price's message of "Sun, 25 Nov 2012 12:30:29 +0000")
Ian Price <ianprice90@googlemail.com> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Instead of using 'null?' and 'cdr' on the syntax object, can you please
>> rework this to use 'syntax-case'? I.e. instead of (if (null? ...) ...)
>> do this:
>>
>> (syntax-case #'(rest ...) ()
>> (() <null-case>)
>> ((name rest ...) <non-null-case>))
>>
>> What do you think?
>
> Yes, that would be much better. It's startling how often I forget I can
> syntax-case this way.
>
> Changed, okay for me to push?
Yes, please push.
Thanks,
Mark
next prev parent reply other threads:[~2012-11-25 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 10:35 Two r6rs bugs Ian Price
2012-11-22 11:38 ` Mike Gran
2012-11-22 12:05 ` Ian Price
2012-11-22 12:18 ` Mike Gran
2012-11-22 21:28 ` Ludovic Courtès
2012-11-23 6:29 ` Mark H Weaver
2012-11-25 12:30 ` Ian Price
2012-11-25 15:58 ` Mark H Weaver [this message]
2012-11-25 16:28 ` Ian Price
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=87d2z11xpr.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.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).