From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: abstracting Lisp strings - macro name convention?
Date: Thu, 4 Jul 2002 01:07:19 -0600 (MDT) [thread overview]
Message-ID: <200207040707.g6477Jq05536@aztec.santafe.edu> (raw)
In-Reply-To: <tx1u1nhwojn.fsf@raeburn.org> (message from Ken Raeburn on Tue, 02 Jul 2002 22:09:00 -0400)
> SMBP is too terse. That won't be used so often
> that we cannot afford a longer and more meaningful name.
Okay, I'll use longer names. Probably something like this set:
It may be good to use short names like SREF and SDATA for the commonly
used accessors. They are used very often. It wasn't the terseness of
the "S", but the terseness of the "MBP", that I see as undesirable.
With a pervasive change like this, do you really want separate
checkins for each file and detailed function-level change log and CVS
log entries for everything affected?
No, there is no need. It is sufficient to describe the changes
in the macros and then say "all references changed."
prev parent reply other threads:[~2002-07-04 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 23:13 abstracting Lisp strings - macro name convention? Ken Raeburn
2002-07-02 7:37 ` Richard Stallman
2002-07-03 2:09 ` Ken Raeburn
2002-07-03 13:13 ` Stefan Monnier
2002-07-03 14:06 ` Kim F. Storm
2002-07-03 13:16 ` Miles Bader
2002-07-03 13:17 ` Henrik Enberg
2002-07-04 7:07 ` 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=200207040707.g6477Jq05536@aztec.santafe.edu \
--to=rms@gnu.org \
--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).