unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: defvar'ing constants
Date: Tue, 28 Jun 2005 09:40:12 +0200	[thread overview]
Message-ID: <f7ccd24b050628004045358b18@mail.gmail.com> (raw)
In-Reply-To: <87vf3zxe9g.fsf-monnier+emacs@gnu.org>

On 6/28/05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> >     For consistency:
> >       (defvar CONSTANT)               ; should work
> >       (defvar CONSTANT ITS-VALUE)     ; should work
> >       (defvar CONSTANT OTHER-VALUE)   ; should fail

> One case I know was consciously make to work is (defvar :foo :foo) so that
> packages using :foo could be kept backward compatible with Emacs-19
> where :foo is a normal variable because keywords don't exist.

Aha, that's why set-default and friends go around a few hoops to allow
setting a keyword to itself. Thanks! Anyway, that was allowed in my
original patch (it's the second case shown above) but I removed it per
Richard's request. I can re-add it if deemed appropriate.

> Whether we should still cater to such thing is another question.

No idea whether it will be usual for people with Emacs 22.X to load
19.X packages :)

-- 
                    /L/e/k/t/u

  reply	other threads:[~2005-06-28  7:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  3:54 defvar'ing constants Juanma Barranquero
2005-06-25  0:31 ` Richard M. Stallman
2005-06-25  4:14   ` Jay Belanger
2005-06-25 13:05     ` Juanma Barranquero
2005-06-25 21:31     ` David Kastrup
2005-06-26  2:28       ` Jay Belanger
2005-08-01  1:39         ` Stephen J. Turnbull
2005-08-01 16:46           ` Richard M. Stallman
2005-06-25 12:59   ` Juanma Barranquero
2005-06-28  5:06   ` Stefan Monnier
2005-06-28  7:40     ` Juanma Barranquero [this message]
2005-06-28 21:29     ` 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

  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=f7ccd24b050628004045358b18@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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 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).