From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Re: cond*
Date: Sat, 23 Dec 2023 07:17:09 +0100 [thread overview]
Message-ID: <CAO48Bk_b48Q+0QHQsNK6zOtj1VVHUx7D5ciqiYp-T1qvLOLa5Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
Richard writes:
> [[[ 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. ]]]
>
> Fall-through clauses are an important feature of cond* and a big
> advance in flexibility. Precisely how to indicate one is a detail,
> and I've proposed three ways to design that:
>
> * A clause with one element.
> * A clause that starts with t.
> * A clause that starts with nil.
> * A keyword.
>
> If you have preferences about that detail, please let me know.
> I am also interested in other suggestions, but I will only accept
> it if it is as natural and simple as those above.
Hi,
wouldn't a clause starting with t be the most natural choice?
Just because it would mimic cond and make things consistent.
My .02cents,
/PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 1545 bytes --]
next reply other threads:[~2023-12-23 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 6:17 Pedro Andres Aranda Gutierrez [this message]
2023-12-25 1:32 ` Re: cond* Bob Rogers
2023-12-25 3:49 ` [External] : " Drew Adams
2023-12-25 4:53 ` Bob Rogers
2023-12-29 3:51 ` Richard Stallman
2023-12-29 7:11 ` Eli Zaretskii
2023-12-31 3:15 ` Richard Stallman
2023-12-29 3:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO48Bk_b48Q+0QHQsNK6zOtj1VVHUx7D5ciqiYp-T1qvLOLa5Q@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.