From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Kelly Dean <kelly@prtime.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why is Elisp's defvar weird? And is eval_sub broken?
Date: Sat, 14 Feb 2015 09:36:16 -0500 [thread overview]
Message-ID: <jwvmw4gd0pl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <miynlVlA0Vcsh6YTYHk4wEPMQ2qNsuPM4rVNaILGIEG@local> (Kelly Dean's message of "Sat, 14 Feb 2015 07:35:58 +0000")
> A declaration of free dynamic variables for a function could tell the
> byte compiler that those free variables aren't typos, since
> otherwise the byte compiler would expect either the symbol to be
> declared special or a lexical variable by that name to be in scope.
There is such a declaration already. It's called (defvar <foo>). Tada!
>> Normally, such conflicts should never happen
>> because all special vars should be named with a "package prefix", but
>> sadly, reality is different, so it was indispensable to make this
>> effect local, to allow lexical-binding code to work reliably.
> By using llet, the byte compiler will catch such conflicts, and your code
> (interpreted or compiled) that uses it will work reliably despite the
> conflicts. This means defvar's weird behavior is no longer needed.
It's not weird once you understand that it's a compiler directive which
is absent from the .elc file.
Stefan
next prev parent reply other threads:[~2015-02-14 14:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:32 Why is Elisp's defvar weird? And is eval_sub broken? Kelly Dean
2015-02-13 19:03 ` Stefan Monnier
2015-02-14 7:35 ` Kelly Dean
2015-02-14 14:36 ` Stefan Monnier [this message]
2015-02-15 14:17 ` Daniel Colascione
2015-02-16 5:42 ` Kelly Dean
2015-02-16 7:40 ` Stefan Monnier
2015-02-17 23:39 ` Kelly Dean
2015-02-18 22:29 ` Stefan Monnier
2015-02-19 10:32 ` Kelly Dean
2015-02-19 13:23 ` Stefan Monnier
2015-02-20 0:11 ` Kelly Dean
2015-02-20 2:02 ` Stefan Monnier
2015-02-22 4:11 ` Proposal for a closed-buffer tracker Kelly Dean
2015-02-22 15:53 ` Eli Zaretskii
2015-02-22 22:03 ` Stefan Monnier
2015-02-22 22:23 ` Dmitry Gutov
2015-02-23 13:53 ` Artur Malabarba
2015-02-23 16:44 ` Eli Zaretskii
2015-02-22 21:59 ` Stefan Monnier
2015-02-28 10:15 ` Artur Malabarba
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=jwvmw4gd0pl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=kelly@prtime.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.