unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13126@debbugs.gnu.org
Subject: bug#13126: 24.3.50; (WISH) Document pcase in Info manual
Date: Thu, 13 Dec 2012 12:37:28 -0500	[thread overview]
Message-ID: <jwv8v91euam.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87fw3a2dy2.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 13 Dec 2012 20:31:57 +0530")

>>> Thanks.  `pcase' seemed a good replacement for `case'.
>> While it's not a plug-in replacement, it provides a superset of the
>> features of case, yes.
> pcase also reminds me of CL's case.  Btw, you know in what version of
> Emacs did pcase made it's appearance.

Probably 24.1.  You'd have to check the NEWS file.

> Provide a BNF and document TERMINALS before NON-TERMINALS. (Currently it
> seems other way round).

I don't think a BNF spec has its place there.  It's fine for the
docstring, but the point of this lispref subsection is to give an
introduction to `pcase'.

> May be replace the example snippets with a /simple/ and /cohesive/
> example.

Do you think snippet 1 is not sufficiently simple?

> I found Snippet 2 "too abstract" and leaves a lot to the
> imagination of the reader.

For those readers not familiar enough with functional programming,
I could tweak it, maybe replacing `call' and `fn' cases with `(neg ,x)
and `(if ,t ,e1 ,e2)?  Would that help?

The problem I see with your snippets is that they're too long.


        Stefan





      reply	other threads:[~2012-12-13 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09  9:28 bug#13126: 24.3.50; (WISH) Document pcase in Info manual Jambunathan K
2012-12-09 17:12 ` Stefan Monnier
2012-12-11 10:20   ` Jambunathan K
2012-12-11 13:55     ` Stefan Monnier
2012-12-13 15:01       ` Jambunathan K
2012-12-13 17:37         ` Stefan Monnier [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv8v91euam.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=13126@debbugs.gnu.org \
    --cc=kjambunathan@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).