From: Dmitry <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: What's the difference between (defvar foo) and (declare (special foo)), with lexical-binding on?
Date: Sun, 27 Jul 2014 12:00:31 +0300 [thread overview]
Message-ID: <86k36zi3bk.fsf@yandex.ru> (raw)
In-Reply-To: <jwvbnsb5icn.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Sun, 27 Jul 2014 04:16:11 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> (declare (special foo))
>
> is a hack defined in CL. It predates lexical-binding and I don't
> think anyone has tried to adapt it to lexical-binding, so I don't know
> what it does in the case of lexical-binding.
Thanks! So, you would advise not to use it in lexical-binding code at
all?
I think the biggest problem with it is it sorta-works-but-not-exactly.
next prev parent reply other threads:[~2014-07-27 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 3:32 What's the difference between (defvar foo) and (declare (special foo)), with lexical-binding on? Dmitry Gutov
2014-07-27 8:16 ` Stefan Monnier
2014-07-27 9:00 ` Dmitry [this message]
2014-07-27 9:58 ` 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=86k36zi3bk.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--cc=help-gnu-emacs@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.
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).