From: Andreas Schwab <schwab@linux-m68k.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.6 released!
Date: Mon, 29 Apr 2013 15:24:00 -0000 [thread overview]
Message-ID: <m2obcxvjbk.fsf@igel.home> (raw)
In-Reply-To: <20130429043214.GV3525@adacore.com> (Joel Brobecker's message of "Mon, 29 Apr 2013 08:32:14 +0400")
Joel Brobecker <brobecker@adacore.com> writes:
> I am still a little fuzzy on what "compatible" means in terms of
> constraints for the enum type.
This is a red herring. Forward-declaring an enum type is a GNU
extension, the C standard does not allow it.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-04-29 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20130426140741.GA13837@adacore.com>
[not found] ` <83k3nptk18.fsf@gnu.org>
2013-04-28 22:59 ` Eli Zaretskii
2013-04-29 9:53 ` Joel Brobecker
2013-04-29 12:48 ` Eli Zaretskii
2013-04-29 14:37 ` Joel Brobecker
2013-04-29 15:24 ` Andreas Schwab [this message]
2013-05-05 19:44 ` Jan Kratochvil
2013-05-06 10:32 ` Joel Brobecker
2013-05-06 16:19 ` Eli Zaretskii
2013-05-06 18:19 ` Tom Tromey
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=m2obcxvjbk.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox