unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@RUM.cs.yale.edu, lektu@terra.es, emacs-devel@gnu.org
Subject: Re: save-match-data woes
Date: Wed, 27 Feb 2002 21:08:08 -0700 (MST)	[thread overview]
Message-ID: <200202280408.g1S488o19225@aztec.santafe.edu> (raw)
In-Reply-To: <Pine.SUN.3.91.1020227120012.21923D-100000@is> (message from Eli Zaretskii on Wed, 27 Feb 2002 12:00:33 +0200 (IST))

    That's true for application code, but what about functions that
    implement core functionality?  The latter can be run from unusual
    places, like all kinds of hooks we have around, in which case it
    should preserve the match data, right?

Some functions have the spirit of a general-purpose facility.  People
will expect those functions to be "clean"--in various ways, so we need
to make them so.  But it is not worth making all functions be "clean"
like that, and people won't expect it.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-02-28  4:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 11:36 save-match-data woes Juanma Barranquero
2002-02-21 11:54 ` Eli Zaretskii
2002-02-22 16:43 ` Stefan Monnier
2002-02-23  5:26   ` Richard Stallman
2002-02-25  8:10   ` Juanma Barranquero
2002-02-25  8:21     ` Stefan Monnier
2002-02-25 10:19       ` Juanma Barranquero
2002-02-26 20:15       ` Richard Stallman
2002-02-27 10:00         ` Eli Zaretskii
2002-02-28  4:08           ` Richard Stallman [this message]
2002-02-26 20:14     ` Richard Stallman

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=200202280408.g1S488o19225@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    --cc=monnier+gnu/emacs@RUM.cs.yale.edu \
    /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).