unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Real constants
Date: Fri, 15 Jul 2005 14:10:58 -0400	[thread overview]
Message-ID: <E1DtUeI-0003EI-A3@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b050714175326400c64@mail.gmail.com> (message from Juanma Barranquero on Fri, 15 Jul 2005 02:53:00 +0200)

    Aren't user-defined constants useful in other languages? Isn't it
    useful per se to be able to set a symbol and guarantee that the user,
    or another module, is not going to change it by accident?

I don't see a need for this.

     Certainly
    Common Lisp is not above having constants

I don't want to add features to Emacs Lisp just because other
languages, even other Lisp dialects, have them.  That would be a
recipe for adding lots more features, each of which would be work to
maintain, work to document, etc.

    What do you ask for? An example? What if the constants define absolute
    sizes of external resources (like, for example,
    `bindat--fixed-length-alist') and every single attempt to change them
    could be considered an error (and possibly crash Emacs)?

That is a case where the feature would provide no practical benefit,
because the magnitude of the problem in practice is zero.  It would be
more elegant in some conceptual sense if these symbols could not be
altered.  But that would not translate into any benefit for Emacs
users, or for us Emacs maintainers.

    No, that's "I assumed the value of real constants in programming
    languages was way beyond needing a rationale"... Perhaps I'm assuming
    too much.

The question here is, "How will they help make Emacs better to edit
with?"

  parent reply	other threads:[~2005-07-15 18:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 13:59 Real constants Juanma Barranquero
2005-07-13 18:14 ` Stefan Monnier
2005-07-13 18:29   ` Juanma Barranquero
2005-07-14  2:25     ` Stefan Monnier
2005-07-14  8:05       ` Juanma Barranquero
2005-07-14  3:14     ` Richard M. Stallman
2005-07-14  8:16       ` Juanma Barranquero
2005-07-15  0:12         ` Richard M. Stallman
2005-07-15  0:53           ` Juanma Barranquero
2005-07-15  9:47             ` Thien-Thi Nguyen
2005-07-15 22:03               ` Richard M. Stallman
2005-07-16 10:10                 ` Juanma Barranquero
2005-07-15 18:10             ` Richard M. Stallman [this message]
2005-07-15  4:24         ` Stefan Monnier
2005-07-18  6:05           ` Juanma Barranquero

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=E1DtUeI-0003EI-A3@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).