From: Alan Mackenzie <acm@muc.de>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: emacs-devel@gnu.org
Subject: Re: Improving aesthetics & readability of backquote
Date: Mon, 20 May 2019 14:02:16 +0000 [thread overview]
Message-ID: <20190520140216.GA4368@ACM> (raw)
In-Reply-To: <m236l9ntqe.fsf@paulwrankin.com>
Hello, Paul.
On Mon, May 20, 2019 at 23:25:13 +1000, Paul W. Rankin wrote:
> On Mon, May 20 2019, Alan Mackenzie wrote:
> > Sorry, I can't make anything out of that paragraph. What meaning?
> > What relation to what? Which code alone?
> The \` symbol is an alias to backquote, and the word "backquote"
> only describes the symbol, i.e. circular semantics.
OK, thanks. "Backquote" partially describes what the operator does,
i.e. it quotes. Sort of.
> >> I suggest that we could introduce some aliases and augment the
> >> reader constucts a little to make them more aesthetically pleasing
> >> and more readable.
> > I don't agree with you that (quote foo) is more readable than 'foo.
> > I would find (quote foo) tiring to write, and (more importantly)
> > tiring to read. I believe very early lisps were lacking the '
> > operator. (quoteval foo) would be even worse for me.
> I'm using "readability" in the sense of reader comprehension, not
> eyestrain.
So was I.
> >> If it remains unclear, my suggestion is not to supplant the
> >> original syntax; I position this suggestion in a similar vein as
> >> the rx library.
The two are different. Regexp strings, like
"\\([{}();:,<]+\\)\\|^\\s *\\(#\\)\\s *define[ \t]+\\(\\sw\\|_\\)+\\([^(a-zA-Z0-9_]\\|$\\)"
are hard to read and decipher. rx is an attempt to make it clearer to
read regexps. On the contrary, ` and , and ,@ are easy to read, the
difficulty being in their semantics.
Back in the 1950s, the language Cobol was invented with just this
premise. It was thought that
ADD 2 TO X GIVING Y
would be easier for beginners (i.e. managers) to understand than
Y = X + 2;
Language design has gone firmly in the opposite direction since then,
emphasising conciseness.
> > But code has to be maintained, and everybody would have to know the
> > meaning of these new aliases, and be practiced with them, to be able
> > to maintain code using them.
> Hence the choice of clear, easily understandable aliases.
I don't think they're easily understandable. They lack the clarity and
distinctiveness of `, ,, and ,@.
> > I'm afraid I'm against such changes.
> I'm proposing an addition, not changes.
An addition is a change, and it would affect all project members. As I
said, I'm against this change.
> See the aforementioned rx library; its relationship to regular
> expression in Emacs Lisp should be instructive.
> --
> https://www.paulwrankin.com
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-05-20 14:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 3:03 Improving aesthetics & readability of backquote Paul W. Rankin
2019-05-20 3:38 ` Stefan Monnier
2019-05-22 15:44 ` Stefan Monnier
2019-05-20 8:52 ` Alan Mackenzie
2019-05-20 13:25 ` Paul W. Rankin
2019-05-20 14:02 ` Alan Mackenzie [this message]
2019-05-20 14:26 ` Paul W. Rankin
2019-05-20 16:08 ` Ken Olum
2019-05-20 23:19 ` Richard Stallman
2019-05-21 2:06 ` Paul W. Rankin
2019-05-21 2:22 ` Noam Postavsky
2019-05-21 2:39 ` Paul W. Rankin
2019-05-21 20:19 ` Richard Stallman
2019-05-22 2:46 ` Paul W. Rankin
2019-05-22 7:56 ` Eli Zaretskii
2019-05-22 8:55 ` Paul W. Rankin
2019-05-22 15:57 ` Michael Heerdegen
2019-05-22 16:13 ` 조성빈
2019-05-22 16:13 ` Michael Heerdegen
2019-05-22 22:40 ` Richard Stallman
2019-05-20 8:59 ` Lars Ingebrigtsen
2019-05-20 13:35 ` Paul W. Rankin
2019-05-20 13:47 ` Basil L. Contovounesios
2019-05-20 14:18 ` Paul W. Rankin
2019-05-20 14:48 ` Basil L. Contovounesios
2019-05-20 15:25 ` Lars Ingebrigtsen
2019-05-20 23:21 ` Richard Stallman
2019-05-21 2:34 ` Paul W. Rankin
2019-05-22 16:14 ` Sam Steingold
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=20190520140216.GA4368@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.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 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).