unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Can't M-x compile-defun `edebug' because dynamic variables are falsely taken as lexical.
Date: Wed, 4 Jan 2017 22:02:43 +0000	[thread overview]
Message-ID: <20170104220243.GC2052@acm.fritz.box> (raw)
In-Reply-To: <jwv37gy4hx4.fsf-monnier+gmane.emacs.devel@gnu.org>

Hello, Stefan.

On Wed, Jan 04, 2017 at 04:49:15PM -0500, Stefan Monnier wrote:
> > special-variable-p would appear to be a near useless function, since it
> > doesn't do what it's name says.

> It's useful for the compiler, but it's mostly internal, indeed.

OK.

> > There appears to be no way of checking whether a variable's binding is
> > (or will be) lexical.

> In which context do you need/want to do that (I ask because how to do
> it (and even if it can be done) depends on the details)?

I honestly don't know.  I presume that there will be code (other than
the byte compiler) which will want to make a distinction.  Maybe there's
not.  After (defvar foo), the byte compiler seems able to handle foo as
a dynamic variable.  I'm still trying to figure out how, given that that
flag denoting a special variable in the struct symbol doesn't get set.

I'm just thoroughly confused about the whole business of whether (defvar
foo) creates a special variable or not.  At the moment, I'm not even
quite sure any more exactly what a special variable is.  I knew this
morning.  :-(

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2017-01-04 22:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 14:14 Can't M-x compile-defun `edebug' because dynamic variables are falsely taken as lexical Alan Mackenzie
2017-01-03 18:35 ` Stefan Monnier
2017-01-03 21:32   ` Alan Mackenzie
2017-01-03 21:48     ` Stefan Monnier
2017-01-04 13:39       ` Alan Mackenzie
2017-01-04 15:23         ` Stefan Monnier
2017-01-04 20:04           ` Alan Mackenzie
2017-01-04 21:49             ` Stefan Monnier
2017-01-04 22:02               ` Alan Mackenzie [this message]
2017-01-04 22:26                 ` Stefan Monnier
2017-01-04 22:44                   ` Drew Adams
2017-01-05 10:54                   ` Alan Mackenzie
2020-02-13 16:42             ` Drew Adams
2020-02-13 20:02               ` Stefan Monnier
2020-02-13 20:43                 ` Drew Adams
2020-02-13 22:09                   ` Stefan Monnier
2020-02-14  1:07                     ` Drew Adams
2020-02-14  2:24                       ` Stefan Monnier
2020-02-14 17:25                         ` Drew Adams
2020-02-14 19:19                           ` Stefan Monnier
2020-02-17 18:23                           ` Drew Adams
2020-02-13 22:11                   ` Stefan Monnier
2020-02-14  1:13                     ` 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

  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=20170104220243.GC2052@acm.fritz.box \
    --to=acm@muc.de \
    --cc=emacs-devel@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.
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).