From: Leo Liu <sdl.web@gmail.com>
To: 20639@debbugs.gnu.org
Subject: bug#20639: 24.5; nesting cl-tagbody
Date: Sun, 24 May 2015 11:56:30 +0800 [thread overview]
Message-ID: <m1iobiiq6p.fsf@gmail.com> (raw)
1. eval the following
(let ((c 10))
(cl-tagbody :next
(cl-tagbody :next
(print c)
(cl-decf c)
(when (zerop (mod c 2))
(go :next)))
(unless (<= c 0)
(go :next))))
2. if: No catch for tag: #:cl--tagbody-tag, :next
Additionally eval the following
(let ((c 10))
(cl-tagbody :next1
(cl-tagbody :next2
(print c)
(cl-decf c)
(when (zerop (mod c 2))
(go :next2)))
(unless (<= c 0)
(go :next1))))
Error: cond: No catch for tag: #:cl--tagbody-tag, cl--exit
Leo
next reply other threads:[~2015-05-24 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 3:56 Leo Liu [this message]
2015-05-25 13:39 ` bug#20639: 24.5; nesting cl-tagbody Stefan Monnier
2015-05-26 4:54 ` Leo Liu
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=m1iobiiq6p.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=20639@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 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).