From: Jean Louis <bugs@gnu.support>
To: Tomas Hlavaty <tom@logand.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: Re: Advantage using mapc over dolist
Date: Tue, 3 Dec 2024 22:38:53 +0300 [thread overview]
Message-ID: <Z09eTdlHt5jYvt2K@lco2> (raw)
In-Reply-To: <87h67ku813.fsf@neko.mail-host-address-is-not-set>
* Tomas Hlavaty <tom@logand.com> [2024-12-03 18:01]:
> On Tue 03 Dec 2024 at 09:11, Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> >>> (pcase actm
> >>> ('armg (do-this))
> >>> ('go (do-that))))
> >>
> >> this does not justify pcase, use ecase or case instead
> >
> > That's your personal preference.
> > My own personal preference is to forget about
> > case/cl/case/ecase/cl-ecase and just use `pcase` like the author
> > already did.
>
> I respect your preference and understand that you as pcase author would
> prefer it everywhere. But whoever renamed case and ecase did not
> respect other peoples preferences and people are now forced to use that
> pcase monstrosity even in very simple cases.
No infection here, no monstrosity on my side, and nobody forced me
anything, in fact I have highest joy with Emacs Lisp.
I remember `dlet*' was like this:
(defmacro rcd-dlet (binders &rest body)
"Like `let*' but using dynamic scoping.
Argument BINDERS behaves similarly like `let' with the difference
that variables become global even under lexical scope.
Optional argument BODY will be executed."
(declare (indent 1) (debug let))
;; (defvar FOO) only affects the current scope, but in order for
;; this not to affect code after the main `let' we need to create a new scope,
;; which is what the surrounding `let' is for.
;; FIXME: (let () ...) currently doesn't actually create a new scope,
;; which is why we use (let (_) ...).
`(let (_)
,@(mapcar (lambda (binder)
`(defvar ,(if (consp binder) (car binder) binder)))
binders)
(let* ,binders ,@body)))
but someone changed it substantially:
(defmacro dlet (binders &rest body)
"Like `let' but using dynamic scoping."
(declare (indent 1) (debug let))
;; (defvar FOO) only affects the current scope, but in order for
;; this not to affect code after the main `let' we need to create a new scope,
;; which is what the surrounding `let' is for.
;; FIXME: (let () ...) currently doesn't actually create a new scope,
;; which is why we use (let (_) ...).
`(let (_)
,@(mapcar (lambda (binder)
`(defvar ,(if (consp binder) (car binder) binder)))
binders)
(let ,binders ,@body)))
That small difference was changed, and I was feeling about you:
(let* ,binders ,@body)
and I complained, because I did not realize how easy it is to make it
how I want, so I stole the function and it is done and well!
In fact, it is possible to make a package aliasing all cl- functions and it is done.
--
Jean Louis
next prev parent reply other threads:[~2024-12-03 19:38 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 23:31 Advantage using mapc over dolist Heime via Users list for the GNU Emacs text editor
2024-12-02 6:26 ` Tomas Hlavaty
2024-12-02 18:30 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 20:41 ` Tomas Hlavaty
2024-12-02 20:50 ` Jean Louis
2024-12-02 21:21 ` Tomas Hlavaty
2024-12-02 21:41 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 6:13 ` Jean Louis
2024-12-03 7:36 ` Tomas Hlavaty
2024-12-03 19:24 ` Jean Louis
2024-12-03 20:04 ` Tomas Hlavaty
2024-12-03 20:09 ` Jean Louis
2024-12-03 20:12 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:24 ` Jean Louis
2024-12-02 20:56 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 19:26 ` Jean Louis
2024-12-03 19:39 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 14:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-03 14:48 ` Tomas Hlavaty
2024-12-03 16:31 ` Stefan Monnier
2024-12-03 17:00 ` Alfred M. Szmidt
2024-12-03 17:24 ` Stefan Monnier
2024-12-03 19:27 ` Tomas Hlavaty
2024-12-03 19:35 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 14:59 ` Tomas Hlavaty
2024-12-03 15:40 ` Tomas Hlavaty
2024-12-03 15:57 ` Tomas Hlavaty
2024-12-03 17:11 ` Eli Zaretskii
2024-12-03 17:33 ` Tomas Hlavaty
2024-12-03 17:40 ` Eli Zaretskii
2024-12-03 17:55 ` Tomas Hlavaty
2024-12-03 18:05 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 18:57 ` Alfred M. Szmidt
2024-12-03 19:06 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:15 ` Tomas Hlavaty
2024-12-04 5:37 ` Alfred M. Szmidt
2024-12-03 19:42 ` Jean Louis
2024-12-03 19:54 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:11 ` Jean Louis
2024-12-03 16:47 ` Stefan Monnier
2024-12-03 18:01 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:05 ` Jean Louis
2024-12-03 20:35 ` Tomas Hlavaty
2024-12-03 23:29 ` Stefan Monnier
2024-12-04 0:57 ` Heime via Users list for the GNU Emacs text editor
2024-12-04 2:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-03 19:38 ` Jean Louis [this message]
2024-12-04 4:56 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-02 6:59 ` Tassilo Horn
2024-12-02 10:12 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-02 17:03 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 18:51 ` Tomas Hlavaty
2024-12-02 20:17 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 21:07 ` Tomas Hlavaty
2024-12-03 13:19 ` Tomas Hlavaty
2024-12-02 21:15 ` [External] : " Drew Adams
2024-12-02 21:58 ` Tomas Hlavaty
2024-12-02 22:42 ` Drew Adams
2024-12-03 5:49 ` Tomas Hlavaty
2024-12-03 20:08 ` Lazy functional programming [was: Advantage using mapc over dolist] Drew Adams
2024-12-03 21:17 ` Tomas Hlavaty
2024-12-04 4:33 ` Advantage using mapc over dolist 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
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=Z09eTdlHt5jYvt2K@lco2 \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tom@logand.com \
/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).