unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: regular expressions that match nothing
Date: Fri, 17 May 2019 08:53:13 -0400	[thread overview]
Message-ID: <jwvmujl2r0e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 20190517094301.GA5011@ACM

> similar long symbols were introduced this would be a pain - a minor pain
> yes, but a pain nevertheless.

While it's long, it's shorter than the cryptic regexp itself if you take
into account the comment that had to accompany the regexp to explain it
and that now is made unnecessary because the name is self-explanatory.

> Why has nobody commented on my suggestion of using re- rather than
> regexp- as the prefix?  We already have re-search-forward.

I recommended "regexp-".  I like brevity and plead guilty of preferring
"-re" (over "-regexp") suffixes in variable names.  Yet I recommended
"regexp-" because it seems to be what Elisp is standardizing on
(e.g. compare `C-h o re- TAB` and `C-h o regexp- TAB`; or look at the
number of variables that were renamed from "-re" to "-regexp") and
I think uniformity and understandability here trumps saving a few chars.
Especially because this is not used very often at all.
Of course, feel free to define `c-nomatch` ;-)

My own favorite is <prefix>-∅ which I believe is the shortest of all the
suggestions I've seen pass by; yet I don't think we want to go that way.

Clearly, this is prime bikeshedding material, so I'll just support the
code author's choice because he was the one who finally did it, after
all these years where it's been mentioned as something we could/should do.


        Stefan




  parent reply	other threads:[~2019-05-17 12:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  7:25 regular expressions that match nothing philippe schnoebelen
2019-05-14 10:14 ` Mattias Engdegård
2019-05-14 19:41   ` Stefan Monnier
2019-05-15 16:21     ` Mattias Engdegård
2019-05-15 19:41       ` Alan Mackenzie
2019-05-16 10:54         ` Mattias Engdegård
2019-05-16 23:18           ` Phil Sainty
2019-05-17  9:43             ` Alan Mackenzie
2019-05-17 10:17               ` Mattias Engdegård
2019-05-17 12:53               ` Stefan Monnier [this message]
2019-05-15 20:17       ` Michael Heerdegen
2019-05-15 21:06         ` Stefan Monnier
2019-05-15 21:07         ` Mattias Engdegård
2019-05-15 21:38           ` Michael Heerdegen
2019-05-16  6:57           ` More re odditie [Was: regular expressions that match nothing] phs
2019-05-16  9:29             ` Mattias Engdegård
2019-05-16 10:59               ` phs
2019-05-16 12:31                 ` Stefan Monnier
2019-05-16 18:35             ` Michael Heerdegen
2019-05-16 20:31               ` Mattias Engdegård
2019-05-16 21:01                 ` Global and local definitions of non-functions/variable (was: More re odditie [Was: regular expressions that match nothing]) Stefan Monnier
2019-05-20 16:26           ` Bootstrap/autoload policy (was Re: regular expressions that match nothing) Mattias Engdegård
2019-05-22 14:02             ` Stefan Monnier
2019-05-22 14:07               ` Mattias Engdegård
2019-05-22 14:24                 ` Stefan Monnier
2019-05-22 15:06                   ` Mattias Engdegård
2019-05-22 15:53                     ` Stefan Monnier
2019-05-22 16:40                       ` Mattias Engdegård
2019-05-22 19:08                         ` Stefan Monnier
2019-05-26 12:05                         ` Basil L. Contovounesios
2019-05-16 18:12       ` regular expressions that match nothing Eric Abrahamsen
2019-05-19  4:30         ` 回复: " net june
2019-05-19  5:00           ` HaiJun Zhang
2019-05-19  7:32             ` Mattias Engdegård
2019-05-20  7:56               ` philippe schnoebelen
2019-05-20 23:19                 ` Richard Stallman
2019-05-19 14:12           ` 回复: " 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=jwvmujl2r0e.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).