From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/cp] method stub assertions
Date: Mon, 05 Jan 2004 02:33:00 -0000 [thread overview]
Message-ID: <20040105023342.GA29313@nevyn.them.org> (raw)
In-Reply-To: <20040105023200.112BF4B35A@berman.michael-chastain.com>
On Sun, Jan 04, 2004 at 09:32:00PM -0500, Michael Chastain wrote:
> > ! struct type *basetype =
> > ! basetype = TYPE_TARGET_TYPE (VALUE_TYPE (arg2));
>
> Argh! But the compilers didn't error out.
> I wonder if that is legal Ansi C?
Yes and no. Semantically valid, value undefined, IIRC. It's part of a
really hideous GCC extension for disabling uninitialized use warnings.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-05 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 2:32 Michael Elizabeth Chastain
2004-01-05 2:33 ` Daniel Jacobowitz [this message]
2004-01-05 11:50 [rfc/cp] take 2: method stubs asserts Michael Elizabeth Chastain
2004-01-05 0:50 ` [rfc/cp] method stub assertions Michael Elizabeth Chastain
2004-01-05 1:56 ` Daniel Jacobowitz
2004-01-05 19:23 ` Daniel Jacobowitz
2004-01-05 20:51 Michael Elizabeth Chastain
2004-01-06 0:12 Michael Elizabeth Chastain
2004-01-06 2:51 ` Daniel Jacobowitz
2004-01-06 4:28 Michael Elizabeth Chastain
2004-01-06 4:43 ` Daniel Jacobowitz
2004-01-06 17:05 ` Daniel Jacobowitz
2004-01-06 18:41 ` David Carlton
2004-01-06 19:05 ` Daniel Jacobowitz
2004-01-06 18:24 Michael Elizabeth Chastain
2004-01-06 19:02 ` Daniel Jacobowitz
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=20040105023342.GA29313@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox