all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "John Wiegley" <johnw@gnu.org>
Cc: michael_heerdegen@web.de, emacs-devel@gnu.org
Subject: Re: Update of pcase docs for the elisp manual
Date: Tue, 26 Jan 2016 22:28:09 +0200	[thread overview]
Message-ID: <83y4bcytk6.fsf@gnu.org> (raw)
In-Reply-To: <m2k2mwgmly.fsf@newartisans.com> (message from John Wiegley on Tue, 26 Jan 2016 11:35:37 -0800)

> From: John Wiegley <jwiegley@gmail.com>
> Cc: michael_heerdegen@web.de,  emacs-devel@gnu.org
> Date: Tue, 26 Jan 2016 11:35:37 -0800
> 
> >> I still vote for "literal" and "logical", since a literal pattern matches
> >> by literally being the same value as the input, while a logical pattern
> >> matches due to the logic of the pattern.
> 
> > 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.

> >> How are they simpler?
> 
> > They are to me. They use undecorated symbols, and don't require the
> > quote/unquote games. If that doesn't explain why they are simpler, then I
> > don't know how to explain it, but the gut feeling is very real.
> 
> Ah, so they are syntactical simpler, but not semantically simpler.

No, they are also semantically different: they allow more generalized
matching rules.

> 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?



  reply	other threads:[~2016-01-26 20: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 [this message]
2016-01-29  1:28                 ` John Wiegley
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=83y4bcytk6.fsf@gnu.org \
    --to=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.