unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340)
Date: Fri, 30 Jun 2017 02:06:33 -0400	[thread overview]
Message-ID: <jwvmv8q9fug.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 87h8yy78bh.fsf@gnu.org

> In CL declaim can be used to make variables special. (In fact, `special'
> is the only declaration that must have an effect in all conforming CL
> implementations.)

Right, AFAIK it's largely equivalent to Elisp's (defvar foo).

not sure how it works in CL, but in Elisp, if a file foo.el has

    (defvar foo)
    ...

then `foo` will be treated as dynamically bound in foo.el when the
compiler generate the code for foo.elc.
But loading foo.elc, won't mark `foo` as dynamically bound, so in

    (require 'foo)
    (defun bar (x)
      (let ((foo x))
        (lambda (y) (+ foo y))))

the function `bar` should treat its `foo` binding lexically.


        Stefan


PS: Note I'm really talking about (defvar foo) and not (defvar foo blabla)




  reply	other threads:[~2017-06-30  6:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170624141528.514.4459@vcs0.savannah.gnu.org>
     [not found] ` <20170624141530.443C5210EB@vcs0.savannah.gnu.org>
2017-06-24 14:26   ` [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340) Stefan Monnier
2017-06-24 14:36     ` Noam Postavsky
2017-06-25 19:34       ` Stefan Monnier
2017-06-29  2:04         ` Noam Postavsky
2017-06-29 11:46           ` Stefan Monnier
2017-06-29 19:25         ` Johan Bockgård
2017-06-29 19:46           ` Noam Postavsky
2017-06-29 20:09             ` Johan Bockgård
2017-06-29 20:49               ` Stefan Monnier
2017-06-29 22:11                 ` Johan Bockgård
2017-06-30  6:06                   ` Stefan Monnier [this message]
2017-07-01  8:59                     ` Johan Bockgård
2017-07-01 14:35                       ` Stefan Monnier
2017-06-29 20:52           ` 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=jwvmv8q9fug.fsf-monnier+gmane.emacs.devel@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 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).