From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 18059@debbugs.gnu.org
Subject: bug#18059: 24.3.92; defvar and special variables
Date: Sun, 11 Mar 2018 15:16:35 -0700 (PDT) [thread overview]
Message-ID: <37ac1e83-64a5-4427-b210-5f718e3affbc@default> (raw)
In-Reply-To: <87h8pmzhl0.fsf@gmail.com>
> So does "end of the current lexical scope" make sense? I think I've
> been looking at this for too long, it's hard for me to tell by now.
>
> Likewise, you can tell the compiler that a variable is defined using
> @code{defvar} with no initial value. (Note that this marks the
> variable as special, i.e.@: dynamically bound, but only until the end
> of the current lexical scope, or file if at top-level.)
... but only _within_ the current lexical scope,
or within the current file if at top-level.
Lexical scope is defined lexically. It can have two
limits or "ends", but it's best to avoid speaking of
beginning and end, as that can suggest temporal end.
https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node43.html
next prev parent reply other threads:[~2018-03-11 22:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 3:23 bug#18059: 24.3.92; defvar and special variables Michael Heerdegen
2018-02-10 19:29 ` Noam Postavsky
2018-02-10 23:59 ` Michael Heerdegen
2018-02-11 0:17 ` Drew Adams
2018-02-11 0:43 ` Noam Postavsky
2018-02-11 0:38 ` Noam Postavsky
2018-02-11 1:32 ` Michael Heerdegen
2018-02-11 2:26 ` Noam Postavsky
2018-02-11 15:14 ` Stefan Monnier
2018-02-11 15:35 ` Noam Postavsky
2018-02-11 16:38 ` Michael Heerdegen
2018-02-11 17:00 ` Noam Postavsky
2018-02-14 0:27 ` Noam Postavsky
2018-02-18 22:28 ` Noam Postavsky
2018-02-19 1:44 ` Michael Heerdegen
2018-02-21 15:09 ` Noam Postavsky
2018-02-21 16:08 ` Drew Adams
2018-02-21 16:23 ` Noam Postavsky
2018-02-21 16:33 ` Noam Postavsky
2018-02-21 17:15 ` Drew Adams
2018-02-21 18:00 ` Noam Postavsky
2018-02-21 19:14 ` Drew Adams
2018-02-21 19:19 ` Stefan Monnier
2018-02-21 22:20 ` Michael Heerdegen
2018-02-23 14:05 ` Stefan Monnier
2018-02-23 14:55 ` Michael Heerdegen
2018-03-04 23:27 ` Noam Postavsky
2018-03-05 9:51 ` Michael Heerdegen
2018-03-07 13:00 ` Noam Postavsky
2018-03-09 9:58 ` Michael Heerdegen
2018-03-09 13:43 ` Stefan Monnier
2018-03-11 16:45 ` Noam Postavsky
2018-03-11 22:16 ` Drew Adams [this message]
2018-03-14 11:15 ` Noam Postavsky
2018-03-23 12:23 ` Noam Postavsky
2018-03-05 15:57 ` Eli Zaretskii
2018-03-08 23:36 ` Noam Postavsky
2018-03-09 0:15 ` Drew Adams
2018-02-21 17:11 ` Drew Adams
2018-02-11 15:57 ` Eli Zaretskii
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=37ac1e83-64a5-4427-b210-5f718e3affbc@default \
--to=drew.adams@oracle.com \
--cc=18059@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@gmail.com \
/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).