From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: mattiase@acm.org, emacs-devel@gnu.org
Subject: Re: Regexp bytecode disassembler
Date: Sun, 22 Mar 2020 18:55:53 +0200 [thread overview]
Message-ID: <83imiwcorq.fsf@gnu.org> (raw)
In-Reply-To: <87sgi05u2w.fsf@gmail.com> (message from Štěpán Němec on Sun, 22 Mar 2020 15:43:03 +0100)
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: mattiase@acm.org, emacs-devel@gnu.org
> Date: Sun, 22 Mar 2020 15:43:03 +0100
>
> IMHO the complexity of `pcase' is completely transparent in this case:
I disagree. And please also consider the easiness (or lack thereof)
of changing the code, not just reading it. pcase is far from being
simple, its syntax is tricky to understand fully. it's no accident
that it took us 2-3 iterations and many discussions to converge on
what is now its documentation. Just the volume of that documentation
should tell you how NOT transparent is its complexity.
> you can easily check the expansion e.g. with M-x
> pp-macroexpand-last-sexp
So you are saying that reading code should be accompanied by expanding
the macros it uses? (Assuming the reader even knows about
pp-macroexpand-last-sexp.) Seriously, I don't think this is something
I'd call "code that explains itself". In any language.
next prev parent reply other threads:[~2020-03-22 16:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 12:27 Regexp bytecode disassembler Mattias Engdegård
2020-03-20 12:58 ` Andreas Schwab
2020-03-20 14:34 ` Eli Zaretskii
2020-03-21 16:52 ` Mattias Engdegård
2020-03-21 19:19 ` Eli Zaretskii
2020-03-21 20:16 ` Štěpán Němec
2020-03-21 20:30 ` Eli Zaretskii
2020-03-21 20:40 ` Mattias Engdegård
2020-03-21 20:44 ` Štěpán Němec
2020-03-22 14:12 ` Eli Zaretskii
2020-03-22 14:43 ` Štěpán Němec
2020-03-22 16:55 ` Eli Zaretskii [this message]
2020-03-22 17:16 ` Štěpán Němec
2020-03-22 17:30 ` Eli Zaretskii
2020-03-22 18:34 ` Paul Eggert
2020-03-22 18:36 ` Dmitry Gutov
2020-03-21 20:50 ` Dmitry Gutov
2020-03-21 23:58 ` Drew Adams
2020-03-22 0:02 ` Drew Adams
2020-03-21 20:37 ` Mattias Engdegård
2020-03-22 3:28 ` Eli Zaretskii
2020-03-22 9:23 ` Mattias Engdegård
2020-03-22 10:37 ` Eli Zaretskii
2020-03-22 15:24 ` Mattias Engdegård
2020-03-22 17:06 ` Eli Zaretskii
2020-03-22 19:39 ` Mattias Engdegård
2020-03-22 20:12 ` Eli Zaretskii
2020-03-22 20:22 ` Corwin Brust
2020-03-20 15:39 ` Pip Cet
2020-03-21 16:56 ` Mattias Engdegård
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=83imiwcorq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=stepnem@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.