From: Andrew Cagney <cagney@gnu.org>
To: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb@sources.redhat.com
Subject: Re: Ada's formats
Date: Wed, 14 Jul 2004 20:00:00 -0000 [thread overview]
Message-ID: <40F58F8A.5060304@gnu.org> (raw)
In-Reply-To: <200407090156.i691uerY026306@tully.CS.Berkeley.EDU>
> Andrew,
>
>
>>> #if 0
>>> {"8#%lo#", "8#", "o", "#"}, /* Octal format info */
>>> {"%ld", "", "d", ""}, /* Decimal format info */
>>> {"16#%lx#", "16#", "x", "#"}, /* Hex format info */
>>> #else
>>> /* Copied from c-lang.c. */
>>> {"0%lo", "0", "o", ""}, /* Octal format info */
>>> {"%ld", "", "d", ""}, /* Decimal format info */
>>> {"0x%lx", "0x", "x", ""}, /* Hex format info */
>>> #endif
>
>
> The problem reflected by the conditionalization here was aesthetic
> internal disagreement as to whether we wanted Ada's literal format for
> hex numbers (e.g., 16#deadbeef#) or C's. GDB sometimes refers to the
> language vector and sometimes does not, so that if our purpose was to
> be kind to the hypothetical GNAT user (i.e., one who believes that "C"
> is just the third letter of the alphabet), we would not only fail, but
> perhaps sow further confusion. The two options remain in the source
> code, however, to indicate the embarrassing fact that we are not of
> one mind on the issue.
> If on the other hand you are asking whether I think that (in general),
> it would improve the abstraction to "functionalize" this part of the
> language vector, my answer is a firm ... could be.
How about this: shall gdb support the feature of language specific
numeric formatting?
If yes, we'll need to make this work. The current code isn't sufficient
so a change such as I suggest will be needed.
If no, we should delete all that broken code - it isn't sufficient to
handle the Ada case.
Here ``could be'' isn't an option :-)
Andrew
next prev parent reply other threads:[~2004-07-14 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 22:25 Andrew Cagney
2004-07-09 1:56 ` Paul Hilfinger
2004-07-14 20:00 ` Andrew Cagney [this message]
2004-07-16 1:14 ` Joel Brobecker
2004-07-16 2:02 ` Andrew Cagney
2004-07-16 4:09 ` Joel Brobecker
2004-07-16 14:20 ` Andrew Cagney
2004-07-16 16:27 ` Joel Brobecker
2004-07-16 21:54 ` Andrew Cagney
2004-08-04 9:04 Paul Hilfinger
2004-08-04 14:41 ` Andrew Cagney
2004-08-11 10:38 ` Paul Hilfinger
[not found] ` <411AA0A9.3060506@gnu.org>
[not found] ` <55713.204.151.174.7.1094055261.squirrel@websd.u-strasbg.fr>
2004-09-02 7:16 ` Paul Hilfinger
2004-09-03 21:30 ` Andrew Cagney
2004-09-03 21:54 ` Paul Hilfinger
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=40F58F8A.5060304@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=hilfingr@EECS.Berkeley.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox