From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: [External] : Re: Re: cond*
Date: Thu, 28 Dec 2023 22:51:39 -0500 [thread overview]
Message-ID: <E1rJ3uN-0005LX-SC@fencepost.gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488D879940089C0714AB0C0F399A@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Mon, 25 Dec 2023 03:49:30 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> * A clause that starts with t.
> Confusion with `cond's very different t.
It's different, but that's the point of the * in cond*.
> * A clause that starts with nil.
> Confusion with `cond's very different nil.
There is no such thibg as "cond's nil". nil is not used to start a
cond clause. We know what it would do there, but we never do that,
because it is useless.
nil as the first element of a cond* clause would act as a waving flag
that says, "Remember, this is different from cond."
> * A keyword.
> Doable, but still not very satisfying, IMO.
Those are the four methods I have thought of. Any of them would work,
so if people prefer the keyword approach, I'll support that one.
If you think of a better way of indicating this feature, please
suggest it to me. If it is clearer, I could use it.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-12-29 3:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 6:17 Re: cond* Pedro Andres Aranda Gutierrez
2023-12-25 1:32 ` Bob Rogers
2023-12-25 3:49 ` [External] : " Drew Adams
2023-12-25 4:53 ` Bob Rogers
2023-12-29 3:51 ` Richard Stallman [this message]
2023-12-29 3:51 ` Richard Stallman
2023-12-29 7:11 ` Eli Zaretskii
2023-12-31 3:15 ` Richard Stallman
2023-12-26 4:03 ` cond* Richard Stallman
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=E1rJ3uN-0005LX-SC@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
/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).