From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: lists, plain conses and length
Date: Thu, 03 Sep 2020 22:26:51 -0400 [thread overview]
Message-ID: <jwvk0xagtwl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20200904022334.791EBC2177B@raman-glaptop.localdomain> (T. V. Raman's message of "Thu, 3 Sep 2020 19:23:34 -0700 (PDT)")
> Q: how does one distinguish a cons from a list.
A: check `null`
(tongue in cheek)
Stefan
PS: Hint: `(listp X)` is the same as `(or (consp X) (null X))`
next prev parent reply other threads:[~2020-09-04 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 2:23 lists, plain conses and length T.V Raman
2020-09-04 2:26 ` Stefan Monnier [this message]
2020-09-04 14:19 ` T.V Raman
2020-09-04 2:29 ` Lars Ingebrigtsen
2020-09-04 8:53 ` tomas
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvk0xagtwl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=raman@google.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).