From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: "Johan Bockgård" <bojohan@gnu.org>, emacs-devel@gnu.org
Subject: Re: Buffer names are sometimes read-only objects in daemonized emacs
Date: Fri, 30 Jul 2010 20:54:15 +0100 [thread overview]
Message-ID: <87mxt89254.fsf@gmail.com> (raw)
In-Reply-To: <201007302041.18983.tassilo@member.fsf.org> (Tassilo Horn's message of "Fri, 30 Jul 2010 20:41:18 +0200")
Tassilo Horn <tassilo@member.fsf.org> writes:
> IMO a function shouldn't need to allow modification of it's return value
> explicitly, but instead should warn if that's possible. But indeed,
> evaluating
>
> (aset (buffer-name) 0 ?g)
How would you do this? I see that the check can be performed on only at
runtime. Bytecompiler will not warn, because the value might be
propagated, and Lisp is dynamicaly typed. (in simple cases like this it
is apparent, but consider just returning this value from function).
Wojciech
next prev parent reply other threads:[~2010-07-30 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 20:30 How do I debug errors in post-command-hook? Tassilo Horn
2010-07-29 21:33 ` Lennart Borgman
2010-07-30 0:11 ` Johan Bockgård
2010-07-30 6:54 ` Tassilo Horn
2010-07-30 11:58 ` Johan Bockgård
2010-07-30 14:23 ` Buffer names are sometimes read-only objects in daemonized emacs (was: How do I debug errors in post-command-hook?) Tassilo Horn
2010-07-30 17:46 ` Buffer names are sometimes read-only objects in daemonized emacs Johan Bockgård
2010-07-30 18:41 ` Tassilo Horn
2010-07-30 19:54 ` Wojciech Meyer [this message]
2010-07-30 20:08 ` Tassilo Horn
2010-07-30 20:46 ` Wojciech Meyer
2010-07-30 21:48 ` Stefan Monnier
2010-07-30 22:07 ` Lennart Borgman
2010-08-01 23:09 ` Stefan Monnier
2010-07-30 23:35 ` Johan Bockgård
2010-08-01 23:10 ` Stefan Monnier
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=87mxt89254.fsf@gmail.com \
--to=wojciech.meyer@googlemail.com \
--cc=bojohan@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tassilo@member.fsf.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).