From: Mark H Weaver <mhw@netris.org>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: [PATCH] %nil-handling optimization and fixes v1
Date: Wed, 2 Sep 2009 12:00:43 -0400 [thread overview]
Message-ID: <20090902160043.GB3310@fibril.netris.org> (raw)
In-Reply-To: <87iqg2nwpk.fsf@arudy.ossau.uklinux.net>
Neil Jerram wrote:
> FWIW, dropping "lisp_" looks OK, but I'm not sure about dropping
> "and_". "scm_is_false_not_nil" feels notably harder to understand
> than "scm_is_false_and_not_nil".
Yes, I see your point, and I agree.
Mark
next prev parent reply other threads:[~2009-09-02 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 16:11 [PATCH] %nil-handling optimization and fixes v1 Mark H Weaver
2009-07-23 21:38 ` Andy Wingo
2009-07-30 22:05 ` Neil Jerram
2009-08-30 9:18 ` Neil Jerram
2009-08-30 18:01 ` Mark H Weaver
2009-09-01 22:09 ` Neil Jerram
2009-09-02 16:00 ` Mark H Weaver [this message]
2009-08-28 7:08 ` Neil Jerram
2009-08-28 7:11 ` Neil Jerram
2009-08-28 7:08 ` Neil Jerram
2009-08-30 13:58 ` Neil Jerram
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=20090902160043.GB3310@fibril.netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=wingo@pobox.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).