all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nic Ferrier <nferrier@ferrier.me.uk>
To: phillip.lord@newcastle.ac.uk (Phillip Lord)
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: A protest against pcase, pcase-let, pcase-let*
Date: Wed, 01 Apr 2015 13:04:23 +0100	[thread overview]
Message-ID: <87k2xw12d4.fsf@ferrier.me.uk> (raw)
In-Reply-To: <87d23ob247.fsf@newcastle.ac.uk> (Phillip Lord's message of "Wed,  01 Apr 2015 10:59:36 +0100")

phillip.lord@newcastle.ac.uk (Phillip Lord) writes:

> 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

I think it's awful, personally.

I don't recall any discussion about whether it would be useful
either. Unlike for, say, the yield stuff which has to be debated
forever.

There are much better, more lisp idiomatic, libs for doing pattern
matching which pcase should give way to imo.

Shadchen for example.


Pattern matching is an excellent tool for programmers. I think pcase is
a poor implementation for EmacsLisp.


Nic



  reply	other threads:[~2015-04-01 12:04 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
2015-04-01 12:04   ` Nic Ferrier [this message]
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=87k2xw12d4.fsf@ferrier.me.uk \
    --to=nferrier@ferrier.me.uk \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@newcastle.ac.uk \
    /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.