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: Another question about lambdas
Date: Sat, 25 Feb 2023 08:31:22 +0100	[thread overview]
Message-ID: <87edqe19rp.fsf@dataswamp.org> (raw)
In-Reply-To: 87h6w3bnwc.fsf@web.de

Michael Heerdegen wrote:

>> Are we talking lexical/static `let' inside or outside
>> `defun's?
>>
>> Inside defuns they are very practical, local variables,
>> basically, outside defuns they are interesting, rather,
>> I have found 2 use cases so far, first, what in other
>> languages are refered to as static variables (whose value
>> don't reset between calls), second, the possibility to
>> share such variables between functions.
>>
>> This file demonstrate those use cases, other than that
>> I don't know what one is supposed to do with them, really,
>> and so far they don't do anything global variables don't.
>> So they are a method to not have those, basically?
>
> Dunno if this is a good summary, I would be careful. I find
> the question a bit artificial - how is the classification
> global vs local functions motivated?

With top-level let-closures "enclosed" defuns can use the
variables defined in the VARLIST of `let' as if they were
global variables, but they are not.

So perceived and real disadvantages of global variables won't
pester your Elisp.

And the advantages are, compared to local variables - also
using `let' - they keep their values between function calls,
and they can be shared/accessed by several functions.

Here is an example showing these two advantages/use cases:
  https://dataswamp.org/~incal/emacs-init/w3m/w3m-survivor.el

If there are other use cases I'm unaware of them.

And if you think about those two use cases, they do nothing
that global variables don't.

So, it's all about avoiding the downsides of global variables?

If so, it's enough - I'll take it. It makes the code more
pretty/cool and you don't use global variables.

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




  reply	other threads:[~2023-02-25  7:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 17:23 Another question about lambdas Michael Heerdegen
2022-12-10 19:33 ` tomas
2022-12-10 20:29   ` Michael Heerdegen
2022-12-10 20:03 ` Emanuel Berg
2022-12-12  1:50   ` Michael Heerdegen
2023-01-18 11:52     ` Emanuel Berg
2023-01-19 13:23       ` Michael Heerdegen
2022-12-10 21:58 ` Arash Esbati
2022-12-11  0:00   ` Michael Heerdegen
2022-12-11  0:09     ` Michael Heerdegen
2022-12-11  7:02     ` tomas
2022-12-12  1:56       ` Michael Heerdegen
2022-12-12  5:24         ` tomas
2022-12-12  6:22           ` Michael Heerdegen
2023-01-18 11:51             ` Emanuel Berg
2023-01-19 13:24               ` Michael Heerdegen
2023-01-19 13:38               ` Michael Heerdegen
2023-01-30 17:44                 ` Emanuel Berg
2023-02-03  0:20                   ` Michael Heerdegen
2023-02-25  7:31                     ` Emanuel Berg [this message]
2023-02-27  8:28                       ` tomas
2023-01-18 11:47           ` Emanuel Berg
2023-01-18 11:33         ` Emanuel Berg
2023-01-19 13:32           ` Michael Heerdegen
2022-12-13 11:26     ` Arash Esbati
2022-12-14  2:22       ` Michael Heerdegen
2022-12-11  0:13 ` Gregory Heytings
2022-12-11  0:38   ` Michael Heerdegen

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