From: Richard Stallman <rms@gnu.org>
Cc: deego@glue.umd.edu, emacs-devel@gnu.org
Subject: Re: patch to emacsbug.el proposed..
Date: Wed, 04 Sep 2002 22:46:55 -0400 [thread overview]
Message-ID: <E17mmfX-00079G-00@fencepost.gnu.org> (raw)
In-Reply-To: <buoznuyle9e.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 04 Sep 2002 10:44:45 +0900)
I don't think just moving some inline code into separate function really
deserves the term `complexity'; it probably even makes the code more
clear. Even if only one person ever uses the new function by itself,
why not do it?
If we encourage him to expect this function to continue to work, in
effect it is part of the specs of Emacs. I do not think it is worth
adding one function to the specs of Emacs for this.
Breaking this subroutine out of the code might be ok if it makes the
code clearer. But if it is a subroutine, people should not expect it
to continue to exist next month. Perhaps we will find a better way to
subroutinize the code.
prev parent reply other threads:[~2002-09-05 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 19:57 patch to emacsbug.el proposed D. Goel
2002-09-02 0:01 ` Richard Stallman
2002-09-02 0:13 ` D. Goel
2002-09-03 13:26 ` Richard Stallman
2002-09-04 1:44 ` Miles Bader
2002-09-05 2:46 ` Richard Stallman [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=E17mmfX-00079G-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=deego@glue.umd.edu \
--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).