GNU bug report logs - #74870
cl-labels and cl-flet don't create named blocks

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#74870: closed (cl-labels and cl-flet don't create named blocks)
Date: Thu, 02 Jan 2025 01:33:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 1 Jan 2025 19:32:46 -0600
with message-id <CADwFkmmofBb4B56LMX7wstDLTZo0=K8WCNZjMCgZQjSHLU6Qiw <at> mail.gmail.com>
and subject line Re: bug#74870: cl-labels and cl-flet don't create named blocks
has caused the debbugs.gnu.org bug report #74870,
regarding cl-labels and cl-flet don't create named blocks
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
74870: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=74870
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Jan Jouleodov <jouleodov <at> protonmail.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: cl-labels and cl-flet don't create named blocks
Date: Fri, 13 Dec 2024 23:30:41 +0000

[Message part 3 (text/plain, inline)]

In ANSI CL, these should create a named CL:BLOCK, allowing one to do a local return via CL:RETURN-FROM. In Emacs, this is not the case, resulting in an uncaught exception.

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 74870-done <at> debbugs.gnu.org,
 Jan Jouleodov <jouleodov <at> protonmail.com>
Subject: Re: bug#74870: cl-labels and cl-flet don't create named blocks
Date: Wed, 1 Jan 2025 19:32:46 -0600

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>>> Is there any reason why one would not want to *always* emulate the CL
>>> behavior in cl-lib? I could only think of a backward compatibility
>>> problem before CL was standardized, but I am not familiar with the time
>>> frame of cl-lib to know if that's really the case.
>> Could you try the patch below?
>
> Never mind, it here's a better one I just pushed to `master`.

I'm therefore closing this bug report.

Previous Next

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