From: Tino Calancha <tino.calancha@gmail.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: Tino Calancha <tino.calancha@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] Implement letrec without backquote?
Date: Sat, 5 Nov 2016 18:05:55 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1611051759370.2397@calancha-pc> (raw)
In-Reply-To: <m260o28g87.fsf@newartisans.com>
On Sat, 5 Nov 2016, John Wiegley wrote:
>>>>>> Tino Calancha <tino.calancha@gmail.com> writes:
>
>> Just for my own education because i am not expert as you, let me ask you,
>> Why do you prefer the original one? Maybe is it more readable?
>
> That's a good question. I think it's because I've written far more macros
> using the former style than the latter, so it reads more naturally to me.
> The "list construction" style is also valid, but has always felt more
> awkward. That said, others might feel exactly the opposite.
I see. Thank you for the explanation. The backquote is very intuitive, i
think more suitable for humans.
My motivation to write that was after reading several old comments in
subr.el like 'do not use backquote here, it's too early'.
Also, i wanted to expand in just one setq call, that is, instead of
(setq x 1) (setq y 2) ... (setq foo N)
like this:
(setq x 1 y 2 ... foo N)
But, it seems it's doesn't bring a better efficiency.
> But in the absence of a definitive style guide, I'd say: stick with what
> we have already.
Fair enough. It's important to keep code style consistency.
> Thanks for the taking the time to submit a patch!
Thanks to you for your answer!
next prev parent reply other threads:[~2016-11-05 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:39 [PATCH] Implement letrec without backquote? Tino Calancha
2016-11-05 8:26 ` John Wiegley
2016-11-05 8:43 ` Tino Calancha
2016-11-05 8:48 ` John Wiegley
2016-11-05 9:05 ` Tino Calancha [this message]
2016-11-05 10:21 ` Andreas Schwab
2016-11-05 11:24 ` Tino Calancha
2016-11-05 17:59 ` Stefan Monnier
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=alpine.DEB.2.20.1611051759370.2397@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@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.