From: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Strange change in bytecmop.el
Date: Tue, 26 Jul 2005 12:09:42 +0200 [thread overview]
Message-ID: <f7ccd24b05072603093e6529ab@mail.gmail.com> (raw)
In-Reply-To: <85y87unegt.fsf@lola.goethe.zz>
On 7/26/05, David Kastrup <dak@gnu.org> wrote:
> So, just _when_ would you use it?
Me? I wouldn't use it. I don't develop packages with XEmacs as the
primary target. I don't ever intend to.
> You just said above that making the distinction only makes sense for
> packages maintained externally.
And so, what? Obviously, if we added the feature 'emacs it *would not*
be for us to use, just to help outside developers. That's the exact
same reason why some functions we've added are XEmacs-compatible (I
just happen to hate the names `define-obsolete-function-alias' and
`define-obsolete-variable-alias', which I would make shorter in a
blink, but they were added as such because XEmacs already define them,
IIRC).
> I don't see that. I am afraid of people putting (boundp 'emacs) into
> code also for things that Emacs happens to have _now_, even though
> XEmacs might gain them in a later synch, or just putting (boundp
> 'emacs) habitually in without thinking anything about it.
That's no different of using "(fboundp 'feature-such-and-such)" for
features Emacs already have. And, worrying about people using things
without thinking smells a bit of patronizing, to me. (No insult
intended, I can assure you.)
> I really think that this is one change that we are better off without.
I didn't propose it, so I'm hardly going to enter a fight for it. I
just happen to think is not only not as outrageous as you made it
sound (when you said "This is so backwards that I consider it
repulsive."), but I even think that could be useful.
--
/L/e/k/t/u
next prev parent reply other threads:[~2005-07-26 10:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 21:49 Strange change in bytecmop.el Stefan Monnier
2005-07-21 23:12 ` Juanma Barranquero
2005-07-22 19:43 ` Stefan Monnier
2005-07-22 22:52 ` Richard M. Stallman
2005-07-23 18:45 ` Stefan Monnier
2005-07-24 14:41 ` Richard M. Stallman
2005-07-24 16:44 ` David Kastrup
2005-07-25 1:43 ` Richard M. Stallman
2005-07-25 1:59 ` David Kastrup
2005-07-25 11:39 ` Robert J. Chassell
2005-07-25 12:51 ` David Kastrup
2005-07-25 16:03 ` Richard M. Stallman
2005-07-25 17:21 ` David Kastrup
2005-07-26 8:12 ` Juanma Barranquero
2005-07-26 8:44 ` David Kastrup
2005-07-26 10:09 ` Juanma Barranquero [this message]
2005-07-26 12:38 ` David Kastrup
2005-07-26 12:58 ` Juanma Barranquero
2005-07-28 22:04 ` Kim F. Storm
2005-07-24 14:41 ` Richard M. 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b05072603093e6529ab@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.