unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 27659@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#27659: 26.0.50; Add string-matched-text: string-match + match-string
Date: Sun, 23 Jul 2017 23:39:54 +0200	[thread overview]
Message-ID: <87k22yde8l.fsf@drachen> (raw)
In-Reply-To: <CAArVCkQXedzbDwXK3sc16QYsRs8wsOMDeUJ36c1aCHbWa3q63w@mail.gmail.com> (Philipp Stephani's message of "Sun, 23 Jul 2017 20:45:34 +0000")

Philipp Stephani <p.stephani2@gmail.com> writes:

> I think the words `form' and `sexp' are used mostly interchangeably
> nowadays, and the docstring of `rx' speaks of "forms" several times.

If you read carefully, then you'll see that the word "form" is only used
in descriptive language.  The only place where something is named "form"
is the argument of `eval', which actually must be a form.

AFAIC, we use the convention that anything called "a form" is normal
Lisp code to be evaluated, especially if an argument of a macro or
special form is named "FORM".  We describe this convention in the
manual.

If you don't follow it, it will confuse others.  It confused me; I
didn't understand what your `let' does until I had a look at the tests.
This is just not necessary.  Enough people already have problems
understanding and accepting pcase stuff, so I think it's extra important
to use unambiguous language.

And BTW, if we choose to give up that naming convention, shouldn't we
first discuss it?


Michael.





      reply	other threads:[~2017-07-23 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  6:13 bug#27659: 26.0.50; Add string-matched-text: string-match + match-string Tino Calancha
2017-07-20  0:54 ` Drew Adams
2017-07-20  1:19   ` Tino Calancha
2017-07-20 19:51 ` Philipp Stephani
2017-07-21 12:29   ` Tino Calancha
2017-07-21 13:34     ` Stefan Monnier
2017-07-21 14:08       ` Tino Calancha
2017-07-21 23:28       ` John Mastro
2017-07-22  2:02         ` Michael Heerdegen
2017-07-23 20:41       ` Philipp Stephani
2017-07-24 14:30         ` Stefan Monnier
2017-07-22  1:46   ` Michael Heerdegen
2017-07-23 20:45     ` Philipp Stephani
2017-07-23 21:39       ` Michael Heerdegen [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=87k22yde8l.fsf@drachen \
    --to=michael_heerdegen@web.de \
    --cc=27659@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=tino.calancha@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).