From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org, emacs-w3m@namazu.org, miles@gnu.org
Subject: [emacs-w3m:07185] Re: bogus change(s) in cl-macs.el
Date: Fri, 19 Nov 2004 14:55:07 +0900 [thread overview]
Message-ID: <b9yfz36o01w.fsf@jpl.org> (raw)
In-Reply-To: b9yllcyv69d.fsf@jpl.org
>>>>>> In [emacs-w3m : No.07180] Miles Bader wrote:
>> Please describe this "breakage" in greater detail.
>>>>> In [emacs-w3m : No.07182] Katsumi Yamaoka wrote:
> From yesterday I'm looking for a simpler way rather than to use
> emacs-w3m to reproduce the bug. However, it has not been
> achieved so far. I'll post it when I found it.
I found the simplest way to explain the bug:
(macroexpand
'(labels ((FOO nil FOO-BODY)
(BAR nil BAR-BODY))
(FOO)
(BAR)))
(let ((--cl---cl-var---- nil)
(--cl---cl-var---- nil))
(progn
(progn
(set '--cl---cl-var---- #'(lambda nil BAR-BODY))
(set '--cl---cl-var---- #'(lambda nil FOO-BODY)))
(funcall (symbol-value '--cl---cl-var----))
(funcall (symbol-value '--cl---cl-var----))))
One of two functions FOO and BAR is disregarded as you see.
When the patch I posted is applied, it will be corrected as
follows:
(let ((--cl-G79813-- nil)
(--cl-G79812-- nil))
(progn
(progn
(set '--cl-G79813-- #'(lambda nil BAR-BODY))
(set '--cl-G79812-- #'(lambda nil FOO-BODY)))
(funcall (symbol-value '--cl-G79812--))
(funcall (symbol-value '--cl-G79813--))))
next prev parent reply other threads:[~2004-11-19 5:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 3:06 bogus change(s) in cl-macs.el Katsumi Yamaoka
2004-11-19 3:41 ` Luc Teirlinck
2004-11-19 3:51 ` Miles Bader
2004-11-19 4:21 ` Luc Teirlinck
2004-11-19 3:48 ` Miles Bader
2004-11-19 3:59 ` Katsumi Yamaoka
2004-11-19 5:55 ` Katsumi Yamaoka [this message]
2004-11-19 7:10 ` Stefan Monnier
2004-11-19 20:04 ` Richard Stallman
2004-11-26 2:17 ` Katsumi Yamaoka
2004-11-26 4:03 ` Stefan Monnier
2004-11-26 5:18 ` Katsumi Yamaoka
2004-11-26 23:51 ` Stefan Monnier
2004-11-19 5:40 ` 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
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=b9yfz36o01w.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-w3m@namazu.org \
--cc=miles@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).