From: Drew Adams <drew.adams@oracle.com>
To: "'Help-Gnu-Emacs (help-gnu-emacs@gnu.org)'" <help-gnu-emacs@gnu.org>
Cc: Emanuel Berg <moasenwood@zoho.eu>
Subject: FW: [External] : Re: Lexical vs. dynamic: small examples?
Date: Sun, 15 Aug 2021 15:42:21 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F1016784ECB7BCF5ABD6F3FC9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: 87y293sdxk.fsf@zoho.eu
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
[Was bitten by Reply All not including the list again...]
> > "Dynamic scope" is a misnomer, BTW; it means only that - no
> > particular scope and dynamic extent [...] `let' provides
> > a lexical binding - the scope ends where the `let'
> > ends, lexically.
>
> But with `let' doesn't the scope end where the let ends even
> for dynamic binding?
No. Dynamic bindings have indefinite scope - that is,
no particular scope.
The binding has dynamic _extent_ - it lasts _as long as_
(time) the code in the `let' body is executing (which
can include nonlocal exits by that code (or code called
by that code) - e.g. `throw').
For such a variable the `let' does not define a scope;
it only determines which code realizes the binding's
duration.
Scope and extent (duration for referencing) are two
different things.
See the CLTL chapter I pointed to.
> If it isn't only about let, what is it about more?
`let' is not the only construct that can define a
scope. For example, a function definition (a `defun'
or a lambda) defines the scope of its formal
parameters - they're lexically scoped.
Again, I recommend that CLTL chapter. It's short, and
it explains things well, including with examples.
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 13542 bytes --]
prev parent reply other threads:[~2021-08-15 15:42 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 3:34 Lexical vs. dynamic: small examples? Eduardo Ochs
2021-08-14 3:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 4:12 ` Eduardo Ochs
2021-08-14 7:35 ` tomas
2021-08-14 16:00 ` Eduardo Ochs
2021-08-14 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:42 ` tomas
2021-08-14 19:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:31 ` tomas
2021-08-14 21:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 21:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 13:35 ` [External] : " Drew Adams
2021-08-14 16:15 ` Eduardo Ochs
2021-08-14 19:00 ` Gregory Heytings
2021-08-14 20:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:23 ` Gregory Heytings
2021-08-14 21:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 21:13 ` tomas
2021-08-14 21:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:41 ` tomas
2021-08-15 0:29 ` [External] : " Drew Adams
2021-08-15 0:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 1:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 1:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 4:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 5:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 15:49 ` Drew Adams
2021-08-15 18:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 21:55 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-15 22:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 21:57 ` Drew Adams
2021-08-15 22:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:54 ` Drew Adams
2021-08-15 23:16 ` Drew Adams
2022-01-09 7:08 ` Jean Louis
2022-01-09 15:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 23:42 ` Arthur Miller
2021-08-15 22:02 ` Lars Ingebrigtsen
2021-08-15 22:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:44 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-21 3:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-24 2:08 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-25 23:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 0:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 0:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 17:01 ` FW: " Drew Adams
2021-08-26 23:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-26 0:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-28 1:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-28 1:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:58 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-15 23:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 23:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-16 0:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 15:42 ` Drew Adams [this message]
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=SJ0PR10MB5488F1016784ECB7BCF5ABD6F3FC9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).