From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Jim Ingham <jingham@apple.com>, gdb-patches@sources.redhat.com
Subject: Re: Trivial fix in value_sub
Date: Wed, 03 Apr 2002 20:11:00 -0000 [thread overview]
Message-ID: <20020403231150.A9816@nevyn.them.org> (raw)
In-Reply-To: <npelhwce3y.fsf@zwingli.cygnus.com>
On Wed, Apr 03, 2002 at 10:54:57PM -0500, Jim Blandy wrote:
>
> Jim Ingham <jingham@apple.com> writes:
> > So... I don't think you should keep the size at 0. This seems like
> > gdb is just silently ignoring the " - x" part of what they typed, and
> > you should always be explicit about what you have done. But if you
> > think an error is more appropriate, I am fine with that...
>
> Oh, no, I didn't mean to suggest that zero was the right size to use;
> I agree with you completely that that would be pretty confusing.
>
> Your story is pretty amazing --- I would never have guessed that
> people actually *use* the sizeof (struct incomplete) == 1 behavior! I
> think it is much more common for people to be unaware that the type is
> incomplete; if this hunch is correct, then the behavior your toolbox
> folks love will be very confusing. I think an error for arithmetic on
> any incomplete type other than (void *) is the right thing.
FWIW, I agree. If we don't know what the size is, we should say so;
having the behavior change based on whether a version of the
implementation (which might have debug symbols) is loaded would be
baffling.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-04 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 15:27 Jim Ingham
2002-04-03 14:52 ` Jim Blandy
2002-04-03 15:55 ` Michael Snyder
2002-04-03 16:11 ` Jim Ingham
2002-04-03 19:55 ` Jim Blandy
2002-04-03 20:11 ` Daniel Jacobowitz [this message]
2002-04-04 13:46 ` Jim Ingham
2002-04-04 14:24 ` Jim Blandy
2002-04-04 15:07 ` Jim Ingham
2002-04-04 15:15 ` Jim Blandy
2002-04-09 17:12 ` Jim Ingham
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=20020403231150.A9816@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jingham@apple.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