all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Effect of lexical binding upon function paramaters
Date: Sat, 05 Nov 2022 17:25:24 +0100	[thread overview]
Message-ID: <87h6zdfjwr.fsf@dataswamp.org> (raw)
In-Reply-To: urRt4FF56GlUl_s7O90bVk5JZ1_ni71doyMAhQYgxM7Mgnyn1i4edgOS4zQKyWWtir72_-324qPbIxDzLRcj2btFD9tICB8eNen9QKkHzBI=@protonmail.com

Heime wrote:

>>> What I can see from this test below, formal parameters
>>> ("arguments" in standard information interchange) are
>>> always dynamic under dynabound, and always static under
>>> lexical
>> 
>> Yup. Same holds for the var bound by `condition-case`.
>> The binding constructs that can be "either/or" are `let`
>> and `let*` (via `lexical-let` for the dynbound dialect and
>> via `defvar` for the lexbound dialect).
>
> So what are we to do

Use lexbound, so far by adding this, as you know

;;; -*- lexical-binding: t -*-

as the first line of every Elisp source file.

Byte-compile the source, it will warn you for unused lexical
variables for example.

Avoid global lexical variables (created with `setq' in the
absence of another variable with the same name), instead use
let-closures for the 'persistent value' (state) and
share-between-functions use cases.

If you desire to create a global variable in the "option"
sense, i.e. you want to introduce something like the
`fill-column' variable, because you imagine it will be used
across a range of functions and different settings (ha), even
be used by future functions - then use `defvar'.

Use `let'/`let*' for function-local variables to organize the
code neatly and break up computations into smaller steps, this
will be the number one use case, however let/let* can also be
used in the "with-option-temporarily-as" sense, in that case
that variable must already exist and be dynamic/special, so
either it is an Emacs option already _or_ you have created it
as described above, with `defvar'.

Note that you can mix this up, let/let* handles it all for you
transparently, just spell everything correctly, okay?

In the example below, we see that `fill-column' is already
a dynamic/special variable, i.e. a global option.
In a lexbound `let', we create "a" and "b" and since they
don't exist they default to lexical. `fill-column' OTOH is
temporarily assigned a new value and remains dynamic/special.

;;; -*- lexical-binding: t -*-

fill-column ; 62

(special-variable-p 'fill-column) ; t, i.e. dynamic/special

(let ((a 1) ; lexical/static
      (b 2) ; lexical/static
      (fill-column 10) ) ; dynamic/special
  (fill-paragraph) ) ; eval me, then change `fill-column' to say 99 and retry

fill-column ; 62

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2022-11-05 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 11:01 Effect of lexical binding upon function paramaters Heime
2022-11-03 13:01 ` Emanuel Berg
2022-11-04 19:30   ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-04 20:23     ` Heime
2022-11-04 20:34       ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-04 20:45         ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-05 16:25       ` Emanuel Berg [this message]
2022-11-05 15:32     ` Emanuel Berg
2022-11-06 20:44       ` Emanuel Berg

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=87h6zdfjwr.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@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 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.