unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: PATCH: Explicitly show how let works on global-variables
Date: Wed, 05 Oct 2022 09:22:02 +1100	[thread overview]
Message-ID: <86lepvut3l.fsf@gmail.com> (raw)
In-Reply-To: <08f6be68d07b1c3ee3c65f8fb6842eb3@webmail.orcon.net.nz>


Phil Sainty <psainty@orcon.net.nz> writes:

> On 2022-10-04 21:09, Pedro Andres Aranda Gutierrez wrote:
>> I understood as local variable a 'value that was stored in the
>> function's stack' to be used in the scope of the let. That implied
>> (once again in my understanding) that the global system-time-locale
>> would not be affected and hence format-time-string would not see the
>> change in the value within the let.
>
> Since the addition of lexical binding to Emacs Lisp in Emacs 24.1,
> both results are possible depending on whether you are dealing with
> a dynamic or a lexical variable.
>
> I.e. given:
>
>  (defun myfunc () foo)
>  (let ((foo 'bar)) (myfunc))
>
> If foo is a dynamic variable then the let form will return 'bar.
>
> If foo is a lexical variable, then you'd get this error:
> "let: Symbol’s value as variable is void: foo".
>
> Eli quoted the manual:
>
>      Local variables created by a ‘let’ expression retain their value
>   _only_ within the ‘let’ expression itself (and within expressions called
>   within the ‘let’ expression); the local variables have no effect outside
>   the ‘let’ expression.
>
> That "(and within expressions called within the ‘let’ expression)" is
> pretty ambiguous wrt dynamic vs lexical binding, and a few lines later
> it comments very briefly on this:
>
>   in Emacs Lisp, the default scoping is dynamic, not lexical.
>   (The non-default lexical binding is not discussed in this manual.)
>
> Which keeps the rest of the text accurate, yet in an almost-entirely
> unexplained manner.
>
> I suggest that at this point it has become pretty necessary for lexical
> binding to be discussed in this manual...
>
> * The *scratch* buffer, in which users will perform many if not most of
>   their experiments, now uses lexical binding by default.
>
> * If enabled, auto-insert-mode adds lexical-binding: t to new elisp files
>   by default.
>
> * IIRC most elisp files in Emacs core are now using lexical binding.
>
> * The emacs-lisp-mode mode-name treats dynamic binding as a warning.
>
> So while it's as true as ever that dynamic binding is the default, the
> fact that so many things nowadays default to *enabling* lexical binding
> really blurs this line, to the point where I think it's unreasonable to
> avoid discussing lexical binding in the introduction to emacs lisp, as
> the user will almost unavoidably be exposed to it.
>
> I think examples would be hugely helpful in explaining the difference
> between the two types of binding.
>

+1. I think this has become quite important.



  parent reply	other threads:[~2022-10-04 22:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  6:46 PATCH: Explicitly show how let works on global-variables Pedro Andres Aranda Gutierrez
2022-10-04  7:52 ` Eli Zaretskii
2022-10-04  8:09   ` Pedro Andres Aranda Gutierrez
2022-10-04 11:36     ` Phil Sainty
2022-10-04 13:43       ` Stefan Monnier
2022-10-04 22:22       ` Tim Cross [this message]
2022-10-05  5:28         ` Pedro Andres Aranda Gutierrez
2022-10-06  9:00           ` Pedro Andres Aranda Gutierrez
2022-10-06 19:34             ` Emanuel Berg
2022-10-04 17:39   ` Richard Stallman
2022-10-04  7:59 ` tomas
2022-10-04 11:56   ` Phil Sainty
2022-10-04 13:48     ` Stefan Monnier
2022-10-05 21:31     ` Richard Stallman
2022-10-04 15:00 ` [External] : " 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=86lepvut3l.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@gmail.com \
    --cc=psainty@orcon.net.nz \
    /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).