GNU bug report logs - #65344
28.2; Unable to Edebug cl-flet form which uses argument destructuring

Previous Next

Package: emacs;

Reported by: Brandon Irizarry <brandon.irizarry <at> gmail.com>

Date: Wed, 16 Aug 2023 18:23:02 UTC

Severity: normal

Found in version 28.2

Fixed in version 30.1

Done: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 65344 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: brandon.irizarry <at> gmail.com, Eli Zaretskii <eliz <at> gnu.org>,
 65344 <at> debbugs.gnu.org
Subject: Re: bug#65344: 28.2; Unable to Edebug cl-flet form which uses
 argument destructuring
Date: Sun, 20 Aug 2023 05:57:37 +0200
Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:

> (debug ((&rest [&or (&define [&name symbolp "@cl-flet@"]
> 			[&name [] gensym] ;Make it unique!
> 			cl-lambda-list
> 			cl-declarations-or-string
> 			[&optional ("interactive" interactive)]
> 			def-body)
> 		    (&define [&name symbolp "@cl-flet@"]
> 			[&name [] gensym] ;Make it unique!
> 			def-body)])

> The second &define is for the (FN EXPR) bindings.  It comes after the
> &define for "normal" function bindings because because, for some
> reason, apparently the second &define also matches the other case.

That's because you use 'def-body' which matches any number of body
expressions.  I think this is not correct: we are expecting a single
form.

Apart from that: yes, something like this... I did not yet understand
the &name magic.

And i wonder whether we should apply the distributive law and factor out
the first few identical specs inside the &or.

Michael.




This bug report was last modified 1 year and 261 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.