From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Anaphoric macros: increase visibility
Date: Sat, 14 Jan 2017 15:15:47 +0500 [thread overview]
Message-ID: <87d1fq9cbw.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1701141655520.2013@calancha-pc> (Tino Calancha's message of "Sat, 14 Jan 2017 16:56:56 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> wrote:
> On Sat, 14 Jan 2017, Dmitri Paduchikh wrote:
>>Comparing if-it, when-it with if-let, when-let, it seems
>>clear that they represent different tradeoffs of simplicity vs. flexibility.
> Do we need to choose? We could have defined both kinds of anaphoric
> macros.
I am not disagree with that. Just wanted to note that existing names of
anaphoric macros are not best ones.
[...]
> Although I prefer your names, i.e., if-it than aif, it might be argued that
> there are historical reasons in favour of the latter.
Well, aif, awhen are at least more discoverable through C-h f aif for those
who used to these names. They can be aliases.
With best regards
Dmitri Paduchikh
next prev parent reply other threads:[~2017-01-14 10:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:39 Anaphoric macros: increase visibility Tino Calancha
2017-01-13 19:48 ` Michael Heerdegen
2017-01-14 2:30 ` Rolf Ade
2017-01-14 2:48 ` Rolf Ade
2017-01-14 3:03 ` Noam Postavsky
2017-01-14 4:13 ` Richard Copley
2017-01-14 5:27 ` Tino Calancha
2017-01-15 0:39 ` Michael Heerdegen
2017-01-15 2:24 ` On the naming/behavior of {if, when}-let (was Re: Anaphoric macros: increase visibility) Mark Oteiza
2017-01-15 2:26 ` Anaphoric macros: increase visibility Michael Heerdegen
2017-01-15 10:24 ` Tino Calancha
2017-01-15 15:32 ` Stefan Monnier
2017-01-16 2:44 ` Tino Calancha
2017-01-16 3:59 ` Stefan Monnier
2017-01-14 6:25 ` Dmitri Paduchikh
2017-01-14 7:56 ` Tino Calancha
2017-01-14 10:15 ` Dmitri Paduchikh [this message]
2017-01-15 0:29 ` Michael Heerdegen
2017-01-15 2:03 ` Dmitri Paduchikh
2017-01-15 2:16 ` Michael Heerdegen
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=87d1fq9cbw.fsf@gmail.com \
--to=dpaduchikh@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=tino.calancha@gmail.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 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.