From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, emacs-devel@gnu.org
Subject: Re: Update of pcase docs for the elisp manual
Date: Thu, 28 Jan 2016 17:28:30 -0800 [thread overview]
Message-ID: <m2twlxqim9.fsf@newartisans.com> (raw)
In-Reply-To: <83y4bcytk6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 26 Jan 2016 22:28:09 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> > AFAIU, your division into logical and literal was different from the
>> > division between UPatterns and QPatterns. That's why I didn't use those
>> > terms.
>>
>> Could you explain a bit more how they were different? Such variance was
>> intended.
> Sorry, I didn't keep your text after I finished working on this. If you send
> it to me again, I will try to explain.
All I meant is, as far as I can tell, UPattern = logical, and QPattern =
literal, without any variation. So isn't it just a name substitution, and
isn't that better than UPattern and QPattern?
>> Ah, so they are syntactical simpler, but not semantically simpler.
> No, they are also semantically different: they allow more generalized
> matching rules.
Different yes, but that's not simpler. The rules for understanding what a
quoted pattern will do are incredibly trivial: it matches per eq with the
scrutinee at that position. The rules of understanding what a UPattern will
do are far more complicated, and can even be extended use pcase-defmacro.
>> Hmm. Maybe we should drop the statement about simplicity and just say we're
>> presenting UPatterns first.
> Like I said: I don't own the manual...
> I do wonder why these minor nits trigger such a large portion of the
> comments. They are there to make the text easier to read, so it isn't too
> dry. If people dislike that style, it's fine with me to delete those parts,
> but what about "the meat"? Did I succeed to write something that can be
> studied and learned from?
Anything, really, is a move forward from what we had before. It's sufficient
for 25.1 in my opinion.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-01-29 1:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2fuxq6pb0.fsf@newartisans.com>
[not found] ` <87d1stznc6.fsf@web.de>
[not found] ` <m2si1p8r31.fsf@newartisans.com>
[not found] ` <m2powt5w50.fsf@newartisans.com>
2016-01-23 11:17 ` Update of pcase docs for the elisp manual Eli Zaretskii
2016-01-24 4:40 ` Stefan Monnier
2016-01-24 14:33 ` Eli Zaretskii
2016-01-24 23:17 ` Stefan Monnier
2016-01-25 16:14 ` Eli Zaretskii
2016-01-26 1:40 ` Stefan Monnier
2016-01-26 15:38 ` Eli Zaretskii
2016-01-26 16:23 ` Stefan Monnier
2016-01-25 14:22 ` Michael Heerdegen
2016-01-25 14:15 ` Michael Heerdegen
2016-01-25 16:33 ` Eli Zaretskii
2016-01-28 18:37 ` Michael Heerdegen
2016-01-29 3:06 ` Stefan Monnier
2016-01-29 9:45 ` Eli Zaretskii
2016-01-29 14:51 ` Michael Heerdegen
2016-01-26 16:59 ` John Wiegley
2016-01-26 18:10 ` Stefan Monnier
2016-01-26 18:41 ` Eli Zaretskii
2016-01-26 19:35 ` John Wiegley
2016-01-26 20:28 ` Eli Zaretskii
2016-01-29 1:28 ` John Wiegley [this message]
2016-01-29 8:30 ` Eli Zaretskii
2016-01-29 13:39 ` Andy Moreton
2016-01-29 14:21 ` Eli Zaretskii
2016-01-29 15:14 ` Andy Moreton
2016-01-29 15:37 ` Eli Zaretskii
2016-01-26 19:58 ` Andy Moreton
2016-01-26 20:19 ` Eli Zaretskii
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=m2twlxqim9.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=michael_heerdegen@web.de \
/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.