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: Thu, 03 Nov 2022 14:01:44 +0100	[thread overview]
Message-ID: <87k04ci43r.fsf@dataswamp.org> (raw)
In-Reply-To: zcJOtcROLbk_PgZ1-Bxs3ikDvWJRZy6-2-egBT2YDrhb38uZfWdagdwnXWTTJa1ft4chSVT8rS4W_JFoOcSOuCV6awblqGr2qt3UNKTuj7w=@protonmail.com

Heime wrote:

> (defun ignition (featr actm)
>   "TODO."
>
>   (when (eq 'sweep featr) (setq featr 'icomplt))
>   (message "%S" featr))
>
> Calling the following sequence of commands
>
> (setq featr 'sweep)
> (ignition featr actm)
> (message "%S" featr)

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
binding, this holds even in the presence of same-named global
variables (and it doesn't matter if they are lexical or
special).

Yeah, too complicated ...

But observe,

;;; -*- lexical-binding: t -*-
;;
;; this file:
;;   https://dataswamp.org/~incal/emacs-init/geh.el

(setq i 1)
(special-variable-p 'i) ; nil

(defvar j 2)
(special-variable-p 'j) ; t

(defun use-i-and-j ()
  (list i j) )

(defun vars-ij (i j)
  (setq i 123123)
  (setq j 666888)
  (use-i-and-j) )

(vars-ij 111111 222222) ; (1 2) lexical
                        ; (123123 666888) dynamic

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




  reply	other threads:[~2022-11-03 13:01 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 [this message]
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

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=87k04ci43r.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.