From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 4643@emacsbugs.donarmstrong.com
Subject: bug#4643: two different definitions for catchlist in eval.c and alloc.c
Date: Wed, 14 Oct 2009 23:14:44 -0400 [thread overview]
Message-ID: <jwvtyy14acp.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <200910141809.n9EI964P024771@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Wed, 14 Oct 2009 11:09:06 -0700 (PDT)")
>> >> Here's a patch that fixes this problem by moving the definition in a
>> >> separate file included in both places.
>> >>
>> >> OK to check in?
>>
>> > Ping.
>>
>> I agree on the idea, but I don't want a new file just for that
>> declaration, so please move it to some existing file instead.
> The catchtag structure definition needs a #include <setjmp.h> to
> precede it. We don't include setjmp.h in many places, so it will need
> to be added... I don't see any existing header that would be a good
> match (other than lisp.h). So please suggest where to add it.
Huh.... lisp.h?
Stefan
next prev parent reply other threads:[~2009-10-15 3:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200910190430.n9J4UFNE012243@godzilla.ics.uci.edu>
2009-10-05 16:18 ` bug#4643: two different definitions for handlerlist and catchlist in eval.c and alloc.c Dan Nicolaescu
2009-10-07 8:32 ` bug#4643: two different definitions for " Dan Nicolaescu
2009-10-14 6:38 ` Dan Nicolaescu
2009-10-14 13:45 ` Stefan Monnier
2009-10-14 18:09 ` Dan Nicolaescu
2009-10-15 3:14 ` Stefan Monnier [this message]
2009-10-15 3:44 ` Dan Nicolaescu
2009-10-15 12:59 ` Stefan Monnier
2009-10-19 4:40 ` bug#4643: marked as done (two different definitions for handlerlist and catchlist in eval.c and alloc.c) Emacs bug Tracking System
2009-10-19 15:55 bug#4643: two different definitions for catchlist in eval.c and alloc.c Adrian Robert
2009-10-19 16:58 ` Dan Nicolaescu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvtyy14acp.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4643@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.