From: Tom Tromey <tromey@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR 7286
Date: Tue, 06 Jan 2009 03:25:00 -0000 [thread overview]
Message-ID: <m3k599f77z.fsf@fleche.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901060247500.23549@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Tue\, 6 Jan 2009 02\:48\:49 +0000 \(UTC\)")
>>>>> "Joseph" == Joseph S Myers <joseph@codesourcery.com> writes:
>> According to C99, such a constant is never unsigned, but instead is of
>> the next wider type (from int, long, and long long) which can
>> represent its value.
Joseph> Note that this is something that changed in C99; in C90 such constants
Joseph> (wider than signed long) would be unsigned.
Thanks.
This does raise the question of what C variant gdb targets, or ought
to target. We could even have them all, with "set lang c99". The
same question arises for C++.
I think if we are going to have a single variant for a given language,
then gdb ought to follow the most recently published standard.
Tom
next prev parent reply other threads:[~2009-01-06 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 0:52 Tom Tromey
2009-01-06 2:48 ` Joseph S. Myers
2009-01-06 3:25 ` Tom Tromey [this message]
2009-01-06 5:59 ` Joseph S. Myers
2009-01-07 19:34 ` 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=m3k599f77z.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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