From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Evil defvars in org.el
Date: Fri, 04 May 2012 20:37:27 -0400 [thread overview]
Message-ID: <jwvipgbbh79.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87wr4rk6rr.fsf@gnu.org> ("Johan Bockgård"'s message of "Fri, 04 May 2012 22:53:12 +0200")
>>> It seems to me that this is something where there really ought to be
>>> a general Emacs solution (dynamic-let or whatever).
>> There is such a thing: (defvar <foo>).
> It currently has a number of problems:
> - The scoping of defvar is unclear and changes when the code is
> compiled:
Indeed, the rules aren't quite the same, which is one of the reasons why
I prefer not to document them. Basically the rule is "leave them at
top-level", which should work just fine in 99.9% of the situations.
> - Invalid byte code is generated when the same symbol is used as both a
> lexical and a dynamic variable:
That one is a bug.
Stefan
next prev parent reply other threads:[~2012-05-05 0:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 3:17 Evil defvars in org.el Chong Yidong
2012-04-27 6:07 ` Bastien
2012-04-27 14:48 ` Bastien
2012-04-27 14:57 ` Edward Reingold
2012-04-27 16:14 ` Bastien
2012-04-27 17:09 ` SAKURAI Masashi
2012-04-27 16:05 ` Glenn Morris
2012-04-27 16:33 ` Drew Adams
2012-04-28 0:15 ` Miles Bader
2012-04-28 0:17 ` Drew Adams
2012-04-28 0:48 ` Miles Bader
2012-04-28 2:25 ` Chong Yidong
2012-05-04 6:56 ` Glenn Morris
2012-05-04 15:29 ` Stefan Monnier
2012-05-04 20:53 ` Johan Bockgård
2012-05-05 0:37 ` Stefan Monnier [this message]
2012-05-05 20:00 ` Glenn Morris
2012-05-07 14:57 ` Stefan Monnier
2012-04-28 2:14 ` Stefan Monnier
2012-04-28 5:57 ` Achim Gratz
2012-04-28 15:10 ` Stefan Monnier
2012-04-28 16:31 ` Achim Gratz
2012-04-28 19:33 ` Stefan Monnier
2012-04-28 6:00 ` Drew Adams
2012-05-08 22:48 ` Martyn Jago
2012-05-09 17:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvipgbbh79.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.