all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Cc: "Mattias Engdegård" <mattiase@acm.org>
Subject: Re: master 9c82f480590: Move and edit text about lexical environment representation
Date: Sun, 22 Oct 2023 06:47:18 +0200	[thread overview]
Message-ID: <87mswbuuuh.fsf@web.de> (raw)
In-Reply-To: <20231021111111.809E3C09BDB@vcs2.savannah.gnu.org> ("Mattias Engdegård"'s message of "Sat, 21 Oct 2023 07:11:11 -0400 (EDT)")

Hello Mattias,

> +Lisp debuggers.  Each member of the list is either a cons cell which
> +represents a lexical symbol-value pair, or a symbol representing a
> +dynamically bound variable.

I have two questions/things that are unclear to me: First, the docstring
of `eval' talks about LEXICAL as an "alist mapping" which seems not to
be exact if it is allowed to contain plain symbols.  Should the
docstring be clarified as well?

Second: you wrote "or a symbol representing a dynamically bound
variable".  Does this variable really have to be bound (to a value), or
do you mean "dynamically binding" (aka special)?  And such a member VAR
in LEXICAL means that the VAR is special when FORM is evaluated - even
when the variable has not been declared special in the outer
context...or something else?

TIA,

Michael.



       reply	other threads:[~2023-10-22  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169788667120.25632.15745430411138121616@vcs2.savannah.gnu.org>
     [not found] ` <20231021111111.809E3C09BDB@vcs2.savannah.gnu.org>
2023-10-22  4:47   ` Michael Heerdegen [this message]
2023-10-22  8:03     ` master 9c82f480590: Move and edit text about lexical environment representation Mattias Engdegård
2023-10-23  3:50       ` Michael Heerdegen
2023-10-23 12:52         ` Mattias Engdegård
2023-10-24  2:12           ` Michael Heerdegen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mswbuuuh.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.