From: David Engster <deng@randomsample.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: bizarre byte-compile issue, possibly due to EIEIO
Date: Mon, 04 Apr 2011 17:26:01 +0200 [thread overview]
Message-ID: <87y63qyr5i.fsf@engster.org> (raw)
In-Reply-To: <87lizqb02q.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 04 Apr 2011 08:47:09 -0500")
Ted Zlatanov writes:
> On Sat, 02 Apr 2011 22:34:33 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>
> LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> So I hope someone can help me out :)
>
> LMI> If it's EIEIO-related, perhaps they can help you out? EIEIO is a
> LMI> mystery to me...
>
> I think it's a problem with the `loop' macro actually but can't isolate
> it in a separate test.
I wasn't able to reproduce the problem without using 'defmethod', so I'm
guessing it's at least related to EIEIO (and maybe also responsible for
the bug). Though it seems to work fine after the lexbind merge, I'm
guessing this is only fixed by side-effect, so there could very well
still a bug be lurking somewhere. I know zero about the byte-compiler,
so I have no idea were to start debugging this.
-David
next prev parent reply other threads:[~2011-04-04 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 20:29 bizarre byte-compile issue, possibly due to EIEIO Ted Zlatanov
2011-04-01 20:31 ` Ted Zlatanov
2011-04-01 20:50 ` Lars Magne Ingebrigtsen
2011-04-02 0:54 ` Ted Zlatanov
2011-04-02 20:34 ` Lars Magne Ingebrigtsen
2011-04-04 13:47 ` Ted Zlatanov
2011-04-04 15:26 ` David Engster [this message]
2011-04-02 21:32 ` David Engster
2011-04-03 9:34 ` David Engster
2011-04-04 10:18 ` Ted Zlatanov
2011-04-04 15:34 ` David Engster
2011-04-05 15:56 ` Ted Zlatanov
2011-04-05 16:38 ` David Engster
2011-04-05 17:55 ` Ted Zlatanov
2011-04-05 18:31 ` David Engster
2011-04-05 18:44 ` Ted Zlatanov
2011-04-05 16:14 ` Ted Zlatanov
2011-04-05 17:57 ` Ted Zlatanov
2011-04-04 16:29 ` 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=87y63qyr5i.fsf@engster.org \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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).