From: Richard Riley <rileyrgdev@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Working with constansts
Date: Mon, 11 May 2009 03:38:49 +0200 [thread overview]
Message-ID: <gu7vj9$j7j$2@news.motzarella.org> (raw)
In-Reply-To: barmar-9F5329.14595610052009@mara100-84.onlink.net
Barry Margolin <barmar@alum.mit.edu> writes:
> In article <mailman.6953.1241976532.31690.help-gnu-emacs@gnu.org>,
> Richard Riley <rileyrgdev@googlemail.com> wrote:
>
>> So really the question would be : why does Lisp not enforce constants
>> being, err, constant?
>
> Because this would incur overhead on every assignment, as it would have
> to check whether the variable being assigned was declared as a constant.
> Since this is so rarely the case, this overhead could be seen as mostly
> wasted and unnecessary.
I don't know enough about Lisp than I can only assume that in this case
it can not be detected at compile time IF you compile to byte/p code.
>
> On the other hand, it would be nice if the byte compiler would warn
> about this. Declaring a constant could put something in its property
> list, and the compiler could then warn if it sees assignments to the
> variable.
>
> Some Common Lisp implementations get around the overhead problem by
> putting constants in a page of VM marked read-only, so a hardware trap
> is raised if an attempt is made to assign it.
This makes sense. My initial enquiry was kind of "yeah, thats the way
you say it is, but should it really be like that". If you get my drift.
next prev parent reply other threads:[~2009-05-11 1:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 15:25 Working with constansts Decebal
2009-05-10 16:19 ` Pascal J. Bourguignon
2009-05-10 16:20 ` Richard Riley
2009-05-10 16:33 ` Pascal J. Bourguignon
2009-05-12 10:34 ` Nikolaj Schumacher
2009-05-10 17:02 ` Drew Adams
2009-05-10 17:28 ` Richard Riley
2009-05-11 7:39 ` Tassilo Horn
[not found] ` <mailman.6953.1241976532.31690.help-gnu-emacs@gnu.org>
2009-05-10 18:17 ` Pascal J. Bourguignon
2009-05-11 1:36 ` Richard Riley
2009-05-11 6:29 ` Pascal J. Bourguignon
2009-05-12 10:06 ` Nikolaj Schumacher
[not found] ` <mailman.7056.1242122790.31690.help-gnu-emacs@gnu.org>
2009-05-12 11:54 ` Pascal J. Bourguignon
2009-05-18 10:55 ` Nikolaj Schumacher
[not found] ` <7ceiuuczad.fsf@pbourguignon.informatimago.com>
[not found] ` <mailman.7379.1242644154.31690.help-gnu-emacs@gnu.org>
2009-05-18 12:20 ` Pascal J. Bourguignon
2009-05-18 19:19 ` Nikolaj Schumacher
2009-05-10 18:59 ` Barry Margolin
2009-05-11 1:38 ` Richard Riley [this message]
2009-05-12 9:44 ` Nikolaj Schumacher
[not found] ` <mailman.7052.1242121473.31690.help-gnu-emacs@gnu.org>
2009-05-12 11:43 ` Pascal J. Bourguignon
2009-05-13 4:59 ` Barry Margolin
2009-05-13 13:41 ` Ralf Wachinger
2009-05-13 21:23 ` Barry Margolin
2009-05-11 9:58 ` Thien-Thi Nguyen
[not found] ` <mailman.6988.1242036217.31690.help-gnu-emacs@gnu.org>
2009-05-12 1:31 ` Barry Margolin
2009-05-11 8:27 ` Decebal
2009-05-12 9:46 ` Nikolaj Schumacher
2009-05-10 16:31 ` Drew Adams
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='gu7vj9$j7j$2@news.motzarella.org' \
--to=rileyrgdev@googlemail.com \
--cc=help-gnu-emacs@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.