From: Drew Adams <drew.adams@oracle.com>
To: Platon Pronko <platon7pronko@gmail.com>, uzibalqa <uzibalqa@proton.me>
Cc: uzibalqa via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: RE: [External] : Determine whether a list is an alist
Date: Thu, 13 Jul 2023 16:14:25 +0000 [thread overview]
Message-ID: <CO6PR10MB54737443738684BA8D9FD86BF337A@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <78ff34f4-a89a-fe18-2681-6eea818b8491@gmail.com>
> There's a consp function that you can use to check
> if entry is cons or not.
And there's its complement, `atom'.
An old-school name, but it says what
it means: "atomic", i.e., indivisible.
But it's only atomic wrt lists. Lisp
now has "atomic" objects that are not
lists but that are in some way divisible.
E.g., a string and a vector are `atom'ic
(they're not `consp'), but you can get
inside them.
So yeah, nowadays `consp' says better
what it means than `atom' does. You
have to read `atom' as just not-a-cons.
next prev parent reply other threads:[~2023-07-13 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 10:40 Determine whether a list is an alist uzibalqa
2023-07-13 14:31 ` [External] : " Drew Adams
2023-07-13 14:40 ` Platon Pronko
2023-07-13 15:40 ` Drew Adams
2023-07-13 15:44 ` Drew Adams
2023-07-13 15:49 ` Platon Pronko
2023-07-13 15:56 ` Drew Adams
2023-07-13 15:57 ` uzibalqa
2023-07-13 16:06 ` Platon Pronko
2023-07-13 16:14 ` Drew Adams [this message]
2023-07-13 16:07 ` Drew Adams
2023-07-13 16:12 ` Robert Pluim
2023-07-13 16:16 ` Drew Adams
2023-07-13 15:59 ` Drew Adams
2023-07-13 14:42 ` uzibalqa
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=CO6PR10MB54737443738684BA8D9FD86BF337A@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=platon7pronko@gmail.com \
--cc=uzibalqa@proton.me \
/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).