From: Michael Heerdegen <michael_heerdegen@web.de>
To: 34481@debbugs.gnu.org
Subject: bug#34481: 27.0.50; cl-flet, cl-labels and lambda expressions
Date: Fri, 15 Feb 2019 03:09:17 +0100 [thread overview]
Message-ID: <87r2c9iz02.fsf@web.de> (raw)
Hi,
two related little issues:
1. `cl-flet's edebug spec only works with one allowed syntax, when all
bindings look like (FUNC ARGLIST BODY...). The second possible syntax
(FUNC EXP) makes edebug barf, no edebugging possible :-(
2. `cl-labels' doesn't allow expressions evaluating to functions. But
I think we could allow lambda expressions. Seems this would not even be
hard to do: the macro constructs a lambda expression anyway (if we do
this, we should take care of the edebug spec as well). Oh - why I want
this? Just a matter of taste, I just prefer a lambda expression to the
(FUNC ARGLIST BODY...) syntax. And I think a (FUNC (lambda ...))
syntax would still be in line with the semantics.
What do you think?
Regards,
Michael.
next reply other threads:[~2019-02-15 2:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 2:09 Michael Heerdegen [this message]
2019-02-19 0:22 ` bug#34481: 27.0.50; cl-flet, cl-labels and lambda expressions Michael Heerdegen
2019-02-19 1:03 ` Michael Heerdegen
2019-02-19 2:36 ` Michael Heerdegen
2019-10-03 22:28 ` Stefan Kangas
2019-10-17 10:36 ` Michael Heerdegen
2019-10-17 10:45 ` Stefan Kangas
2019-10-17 12:31 ` Michael Heerdegen
2019-10-17 18:20 ` Michael Heerdegen
2019-11-07 13:44 ` Stefan Kangas
2021-03-01 15:53 ` Lars Ingebrigtsen
2021-03-01 16:23 ` Stefan Monnier
2021-03-01 23:15 ` Michael Heerdegen
2021-03-01 23:18 ` Michael Heerdegen
2021-03-01 23:29 ` Lars Ingebrigtsen
2021-03-01 23:49 ` Michael Heerdegen
2021-03-02 1:11 ` Michael Heerdegen
2021-03-02 6:53 ` Lars Ingebrigtsen
2021-03-02 2:41 ` Stefan Monnier
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=87r2c9iz02.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34481@debbugs.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.