From: "João Távora" <joaotavora@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,
Michael Heerdegen <michael_heerdegen@web.de>,
akater <nuclearspace@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Some improvements for cl-flet
Date: Mon, 11 Oct 2021 22:26:33 +0100 [thread overview]
Message-ID: <CALDnm51UW4qApTEVK=eZzpVaQbUg2v3KE2dXT7e9jQBr5C9DDg@mail.gmail.com> (raw)
In-Reply-To: <E1ma2f4-0006En-F9@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
On Mon, Oct 11, 2021 at 10:21 PM Richard Stallman <rms@gnu.org> wrote:
> > Yes, but SYMBOL-MACROLET is relatively common in Common Lisp programs,
> > which in itself warrants its inclusion in a Common Lisp emulation
> > library, IMO.
>
> I am sure you know what you're referring to. But I am shocked this
> would be used frequently. Can you plesae show me why and how?
I'm not going to answer for Po Lu, but I'll only mention something not yet
said about this form, which is that it is so important to the Common Lisp
language that it's not even a macro, it's one of the fundamental "special
forms" of the language (added sometime in 1988, it seems).
João
[-- Attachment #2: Type: text/html, Size: 1067 bytes --]
next prev parent reply other threads:[~2021-10-11 21:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 12:51 Some improvements for cl-flet akater
2021-09-11 23:32 ` Michael Heerdegen
2021-09-12 3:35 ` akater
2021-09-12 15:38 ` Stefan Monnier
2021-09-13 0:14 ` Michael Heerdegen
2021-09-13 2:26 ` Stefan Monnier
2021-10-07 2:32 ` akater
2021-10-07 18:03 ` Stefan Monnier
2021-10-08 21:57 ` Richard Stallman
2021-10-09 5:23 ` akater
2021-10-09 6:01 ` Michael Heerdegen
2021-10-09 23:37 ` Richard Stallman
2021-10-10 10:41 ` Po Lu
2021-10-10 20:27 ` João Távora
2021-10-10 21:57 ` Stefan Monnier
2021-10-11 0:45 ` [External] : " Drew Adams
2021-10-11 21:16 ` Richard Stallman
2021-10-11 21:26 ` João Távora [this message]
2021-10-12 22:42 ` Richard Stallman
2021-10-12 0:05 ` Po Lu
2021-10-12 0:29 ` Robin Tarsiger
2021-10-12 22:43 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-14 4:00 ` Michael Heerdegen
2021-09-23 22:37 ` [PATCH] " akater
2021-09-23 22:41 ` akater
2021-09-24 7:11 ` João Távora
2021-09-24 15:20 ` [PATCH] Some improvements for cl-flet, and some more akater
2021-09-24 16:22 ` João Távora
2021-09-25 1:28 ` Lars Ingebrigtsen
2021-09-25 8:37 ` João Távora
2021-09-24 20:30 ` [PATCH] Some improvements for cl-flet akater
2021-09-26 6:54 ` Lars Ingebrigtsen
2021-09-26 12:04 ` akater
2021-09-26 12:36 ` Lars Ingebrigtsen
2021-10-03 3:51 ` Stefan Monnier
2021-10-07 5:02 ` akater
2021-10-07 18:23 ` Stefan Monnier
2021-11-03 12:59 ` akater
2021-11-09 20:37 ` Stefan Monnier
2021-10-09 5:33 ` akater
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='CALDnm51UW4qApTEVK=eZzpVaQbUg2v3KE2dXT7e9jQBr5C9DDg@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=nuclearspace@gmail.com \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).