unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Effect of lexical binding upon function paramaters
Date: Sun, 06 Nov 2022 21:44:36 +0100	[thread overview]
Message-ID: <87edufbyob.fsf@dataswamp.org> (raw)
In-Reply-To: 87o7tlfmcm.fsf@dataswamp.org

> So is it all about what let/let* defaults to? [...]

So for completeness we need:

slet  - always static let

salet - static-adaptive let, defaults to static but don't
        change dynamic global binidngs with the same name,
        but binds new value for its reach

alet  - adaptive let, defaults to static if `lexical-binding'
        (which itself defautls to t), else defautls to
        dynamic. Also don't change existing globals from
        either binding styles into the other. (alet/alet* are
        also aliased from `let'/`let*'.)

dalet - dynamic-adaptive let, defaults to dynamic, don't
        change static

dlet  - always dynamic

For clarity and practical day-to-day use we need:

Alias 'locals' to slet (locals as in local variables).

A wrapper function or macro called 'opts' (as in "with options
as") which will first check if such an option has been defined
as a dynamic/special variable (i.e. with `defvar' or already
existing in Emacs as an option, possibly defined in C even),
and if all do exit it will just be like `dlet' and new values
will be assieged for its reach and duration.

So then the code would look like this

(locals ((x 5)
         (y 8) )
  ;; ...
  (opts ((fill-column 10))
    (fill-paragraph) )
  ;; ... )

and slet, salet, alet, dalet and dlet would seldom be used, at
least not directly, but they would be there for anyone who'd
want them.

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




      reply	other threads:[~2022-11-06 20:44 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
2022-11-05 15:32     ` Emanuel Berg
2022-11-06 20:44       ` Emanuel Berg [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=87edufbyob.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.
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).