From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : How to create a higher order function?
Date: Sun, 26 Sep 2021 01:48:51 +0200 [thread overview]
Message-ID: <87mto0usgs.fsf@zoho.eu> (raw)
In-Reply-To: 87tui99n63.fsf@mbork.pl
Marcin Borkowski wrote:
>>> RMS's arguments are specifically for users of an editing
>>> environment such as Emacs. They go beyond the general
>>> arguments for providing dynamic binding (in addition to
>>> lexical) in Lisp.
>>
>> Again, if it is the options argument I agree that's a good
>> method to do it however I would formulate that as "we
>> implement options by way of global variables", I don't see
>> how dynamic/special vs static/lexical really applies?
>
> IIUC, if these (global) variables were lexically bound, the
> whole idea wouldn't work.
Global variables are present in many languages that do not
mention dynamic/special vs static/lexical.
> Global/local has nothing to do with it.
If they were local, how would people set them? Also if they
were local, how would developers add e.g. another function
that used them?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-09-25 23:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 4:10 How to create a higher order function? Marcin Borkowski
2021-09-21 4:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-21 5:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-21 11:27 ` Leo Butler
2021-09-21 11:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-21 20:31 ` mm-uu-extract was: " Leo Butler
2021-09-21 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-24 9:02 ` Marcin Borkowski
2021-09-24 9:00 ` Marcin Borkowski
2021-09-21 15:49 ` [External] : " Drew Adams
2021-09-24 9:04 ` Marcin Borkowski
2021-09-24 9:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-24 16:50 ` Drew Adams
2021-09-24 17:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-25 6:36 ` Marcin Borkowski
2021-09-25 23:48 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-09-27 10:10 ` Marcin Borkowski
2021-09-28 1:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 17:14 ` Marcin Borkowski
2021-09-29 4:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-05 7:25 ` Marcin Borkowski
2021-10-05 7:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-05 9:53 ` dlet/let/slet (was: Re: [External] : How to create a higher order function?) Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 19:03 ` How to create a higher order function? Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-22 20:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 23:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-24 8:57 ` Marcin Borkowski
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=87mto0usgs.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).