From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: pcase without code duplication
Date: Fri, 23 Apr 2021 05:24:05 +0200 [thread overview]
Message-ID: <877dktel9m.fsf@telefonica.net> (raw)
In-Reply-To: trinity-0c6e8de4-4cac-4bd5-b7ac-d5cc5a2c8b89-1619145939348@3c-app-mailcom-bs16
michael-franzese@gmx.com writes:
> I am using pcase, but am wondering whether I can have pcase
> for 0 and 2 do the same things without adding a separate pcase
> (0 and duplicating the statements.
>
> (pcase orthogr-region
> (0 ... ) ; same operations as pcase 2
> (1 ... )
> (2 ... ) ; operations
> (_ ... ) )
(let ((xx 2))
(pcase xx
(1 (message "one"))
((or 0 2) (message "zero or two"))
(_ (message "something else"))))
next prev parent reply other threads:[~2021-04-23 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 2:45 pcase without code duplication michael-franzese
2021-04-23 3:24 ` Óscar Fuentes [this message]
2021-04-23 3:45 ` michael-franzese
2021-04-23 4:01 ` Stefan Monnier
2021-04-23 3:51 ` [External] : " Drew Adams
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=877dktel9m.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=help-gnu-emacs@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.
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).