From: Daniel Kraft <d@domob.eu>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: %nil once again
Date: Fri, 31 Jul 2009 07:05:42 +0200 [thread overview]
Message-ID: <4A727BA6.7000604@domob.eu> (raw)
In-Reply-To: <878wi5yh5w.fsf@arudy.ossau.uklinux.net>
Neil Jerram wrote:
> Andy Wingo <wingo@pobox.com> writes:
>
>>> Other things needed would be for instance terminating rest-arguments
>>> by %nil rather than '() and the like.
>
> Why is that needed? I.e. Why is it important for a rest argument to
> be terminated with %nil instead of with () ?
Well, I don't think it is "important" at all, but it would be needed for
"complete elisp" semantics, just because it is a list and lists should
be terminated by %nil in elisp. Someone might try to check for the
end-of-list with (eq tail nil) instead of (null tail) and it should
still work.
BTW, for an empty rest argument the elisp documentation explicitly
states it "should" be nil (well, but that's obviously so because nil is
the empty list).
Daniel
--
Done: Arc-Bar-Cav-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Kni-Mon-Pri
prev parent reply other threads:[~2009-07-31 5:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 13:47 %nil once again Daniel Kraft
2009-07-17 7:59 ` Neil Jerram
2009-07-17 9:02 ` Daniel Kraft
2009-07-17 14:20 ` Andreas Rottmann
2009-07-19 18:28 ` Neil Jerram
2009-07-19 19:44 ` Daniel Kraft
2009-07-19 20:10 ` Neil Jerram
2009-07-20 3:33 ` Ken Raeburn
2009-07-20 8:12 ` Daniel Kraft
2009-07-20 9:15 ` Ken Raeburn
2009-07-23 22:18 ` Andy Wingo
2009-07-20 18:17 ` Clinton Ebadi
2009-07-30 21:38 ` Neil Jerram
2009-07-31 5:03 ` Daniel Kraft
2009-07-23 20:35 ` Andy Wingo
2009-07-24 6:20 ` Daniel Kraft
2009-07-30 21:50 ` Neil Jerram
2009-07-31 5:05 ` Daniel Kraft [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=4A727BA6.7000604@domob.eu \
--to=d@domob.eu \
--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).