unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: tsdh@gnu.org, tom@tromey.com, 61395@debbugs.gnu.org
Subject: bug#61395: 28.2; bug-reference warning seems incorrect
Date: Sat, 11 Feb 2023 08:56:44 -0700	[thread overview]
Message-ID: <875yc8gpqb.fsf@tromey.com> (raw)
In-Reply-To: <87edqw1r86.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sat, 11 Feb 2023 10:33:29 +0100")

Kévin> (I've since learned that "too far" really means "one function call away,
Kévin> if that function is declared neither 'pure nor 'side-effect-free")

It'd be good to have an alternative regexp API that doesn't suffer from
these problems.  Both regexps themselves and match-data could just be
ordinary objects instead of hidden things.

Tom





  reply	other threads:[~2023-02-11 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 19:08 bug#61395: 28.2; bug-reference warning seems incorrect Tom Tromey
2023-02-10  8:25 ` Eli Zaretskii
2023-02-10 15:02   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 15:54     ` Tassilo Horn
2023-02-10 16:27       ` Tom Tromey
2023-02-10 17:21         ` Tassilo Horn
2023-02-10 18:10           ` Tom Tromey
2023-02-10 18:15             ` Tassilo Horn
2023-02-10 18:32               ` Tom Tromey
2023-02-11  9:33               ` Kévin Le Gouguec
2023-02-11 15:56                 ` Tom Tromey [this message]
2023-02-10 18:25           ` Tom Tromey
2023-02-10 16:41   ` Tom Tromey

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=875yc8gpqb.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=61395@debbugs.gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=tsdh@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).