From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: A protest against pcase, pcase-let, pcase-let*
Date: Wed, 01 Apr 2015 10:59:36 +0100 [thread overview]
Message-ID: <87d23ob247.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <20150331180029.GF2871@acm.fritz.box> (Alan Mackenzie's message of "Tue, 31 Mar 2015 18:00:29 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Can we please have a moratorium on the use of pcase, etc.? Their use is
> gradually proliferating through Emacs, yet they are not documented.
>
> OK, maybe pcase itself has a page in the elisp manual, but this page is
> very difficult to understand, certainly for me. I have attempted quite
> a lot of times to make sense of it, and failed.
>
> There are two possibilities here: (i) the page is difficult because
> pcase is itself difficult. In this case we should stop using pcase and
> systematically remove it from Emacs source. (ii) The page is difficult
> because it is not well written. In this case it should be improved.
> Personally, I think (ii) is more likely to be true than (i).
The documentation is, I think, written from the perspective of someone
who knows what this sort of pattern-matching does already. The elisp
manual is, of course, a manual rather than a tutorial and the pcase
documentation is particularly not an easy read.
The emacs-wiki has tons of examples, which is much easier to understand
I think!
http://www.emacswiki.org/emacs/PatternMatching
next prev parent reply other threads:[~2015-04-01 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:00 A protest against pcase, pcase-let, pcase-let* Alan Mackenzie
2015-03-31 18:29 ` John Wiegley
2015-04-18 1:47 ` Ted Zlatanov
2015-03-31 19:25 ` Dmitry Gutov
2015-04-01 7:46 ` Daniel Colascione
2015-04-01 9:59 ` Phillip Lord [this message]
2015-04-01 12:04 ` Nic Ferrier
2015-04-01 12:16 ` Dmitry Gutov
2015-04-01 13:53 ` Stefan Monnier
2015-04-02 7:19 ` Richard Stallman
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=87d23ob247.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
/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.