From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"brandon.irizarry@gmail.com" <brandon.irizarry@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
"65344@debbugs.gnu.org" <65344@debbugs.gnu.org>
Subject: bug#65344: 28.2; Unable to Edebug cl-flet form which uses argument destructuring
Date: Fri, 25 Aug 2023 06:07:47 +0200 [thread overview]
Message-ID: <87il93kbn0.fsf@web.de> (raw)
In-Reply-To: <CO6PR10MB54736C49D59CAA2AB4F721DEF3E3A@CO6PR10MB5473.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 25 Aug 2023 01:53:50 +0000")
Drew Adams <drew.adams@oracle.com> writes:
> If something is somewhat like a CL construct,
> but it is intentionally different in some way
> (and not just because we've implemented only
> partial support for it), then why use the
> prefix `cl-' for it? Why not use the prefix
> `el-' or whatever?
That would be much more confusing IMO. `cl-flet' is not just "somewhat
like a CL construct". "cl inspired" would be a bad description. The
manual clearly describes the limits of the "emulation", and, as I said,
even more limiting incompatibilities do not stem from such extensions.
> Nothing says that Elisp needs to have the
> same things as CL. But why call something
> different "CL support" or "CL emulation", and
> use the same prefix, `cl-', that we use for
> things that are really intended to emulate
> CL constructs?
The library is somewhere between an "CL emulation" and a "CL inspired
extension library". It is hard to find a really good name and
description.
> It's like we have no guideline or map now.
Naming being hard or not satisfactory doesn't imply anything. I doesn't
tell what we must do. It just means it is hard to find a "perfect for
everybody" name. That naming something is hard might mean that there is
a problem with that thing, or it might mean nothing.
> To what avail? There's no shortage of
> prefixes and nothing forcing things with
> different purposes or natures to be in the
> same file.
Changing this prefix would cause work and trouble. If you think it is
worth it - what's your suggestion? "el-" is much worse. What in `flet'
is more "Emacs Lisp"y than in `let'? Everything in Emacs Lisp is Emacs
Lisp. The "Emacs Lisp" version of `flet'? Of which `flet'? Ahh - of
the Common Lisp `flet' - but it's only 99.9% compatible, so we don't
call it "cl-".
This line of argument is not convincing me. If a user has looked at the
documentation (one has to anyway to get a start), the "cl-" is also
hardly a source of confusion. So I still don't see a relevant problem.
Michael.
next prev parent reply other threads:[~2023-08-25 4:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:21 bug#65344: 28.2; Unable to Edebug cl-flet form which uses argument destructuring Brandon Irizarry
2023-08-17 0:55 ` Michael Heerdegen
2023-08-17 5:29 ` Gerd Möllmann
2023-08-17 15:42 ` Brandon Irizarry
2023-08-17 15:56 ` Eli Zaretskii
2023-08-17 18:23 ` Gerd Möllmann
2023-08-17 23:07 ` Michael Heerdegen
2023-08-18 5:19 ` Gerd Möllmann
2023-08-18 5:58 ` Michael Heerdegen
2023-08-18 6:43 ` Gerd Möllmann
2023-08-19 8:08 ` Gerd Möllmann
2023-08-20 3:57 ` Michael Heerdegen
2023-08-20 5:32 ` Gerd Möllmann
2023-08-20 6:08 ` Michael Heerdegen
2023-08-20 6:48 ` Gerd Möllmann
2023-08-21 1:19 ` Michael Heerdegen
2023-08-21 7:01 ` Gerd Möllmann
2023-08-21 7:10 ` Gerd Möllmann
2023-08-21 7:30 ` Gerd Möllmann
2023-08-22 0:54 ` Michael Heerdegen
2023-08-22 5:48 ` Gerd Möllmann
2023-08-22 6:10 ` Michael Heerdegen
2023-08-22 8:05 ` Gerd Möllmann
2023-08-22 21:06 ` Brandon Irizarry
2023-08-23 0:35 ` Michael Heerdegen
2023-08-23 0:32 ` Michael Heerdegen
2023-08-23 1:25 ` Drew Adams
2023-08-23 6:06 ` Gerd Möllmann
2023-08-23 14:23 ` Drew Adams
2023-08-24 3:16 ` Michael Heerdegen
2023-08-24 9:10 ` Gerd Möllmann
2023-08-24 23:04 ` Michael Heerdegen
2023-08-25 1:53 ` Drew Adams
2023-08-25 4:07 ` Michael Heerdegen [this message]
2023-08-25 14:50 ` Drew Adams
2023-08-26 0:16 ` Michael Heerdegen
2023-08-26 2:02 ` Drew Adams
2023-08-20 4:39 ` Michael Heerdegen
2023-08-20 5:15 ` Gerd Möllmann
2023-08-23 9:25 ` Mattias Engdegård
2023-08-23 9:31 ` Mattias Engdegård
2023-08-23 11:10 ` Gerd Möllmann
2023-08-23 14:08 ` Gerd Möllmann
2023-08-24 1:14 ` Michael Heerdegen
2023-08-24 6:17 ` Gerd Möllmann
2023-08-25 4:10 ` Michael Heerdegen
2023-08-25 6:19 ` Gerd Möllmann
2023-08-25 4:22 ` Michael Heerdegen
2023-08-25 6:33 ` Gerd Möllmann
2023-08-25 17:53 ` Michael Heerdegen
2023-08-26 5:39 ` Gerd Möllmann
2023-08-27 4:02 ` Michael Heerdegen
2023-08-27 6:34 ` Gerd Möllmann
2023-09-01 23:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 5:10 ` Gerd Möllmann
2023-09-02 17:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 19:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 5:51 ` Gerd Möllmann
2023-09-03 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 16:47 ` Gerd Möllmann
2023-09-04 21:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-23 9:33 ` Gerd Möllmann
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=87il93kbn0.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65344@debbugs.gnu.org \
--cc=brandon.irizarry@gmail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.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.
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).