Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] patch to remove language-dependent numeric output support
Date: Sat, 11 Sep 2004 02:03:00 -0000	[thread overview]
Message-ID: <41425E6F.4050607@gnu.org> (raw)
In-Reply-To: <20040911003752.B1A86F2D86@nile.gnat.com>

> [Ooops.  I see my previous Subject line was a bit mangled.  So here is
> the same patch with a more meaningful subject.]

Think your self lucky - my disk failed and ate it :-)

> At Andrew's request, I've prepared a patch that removes the
> (essentially unused) features in the language vector and elsewhere
> that provide for language-dependent integral output formats.  The
> patch below causes GDB to use C-format throughout instead.  This change
> does indeed allow for a bit of brush removal.
> 
> The idea is that if language-specific formatting were ever to be
> re-introduced, it would be via a function in the language vector. (I'd
> suggest that such a function take a raw string of digits and perhaps
> their radix, and work from that.  For C, it would stick 0x or 0 in
> front, according to radix and value; for Ada, it would stick RADIX# in
> front and # after for non-decimal radices).
> 
> The patch would have been a lot shorter, but several name changes seemed 
> indicated.  Comments solicited.

the code changes are ok - the language specific changes being mindless 
follow suit (and I think I'll have a drink, thanks!).

Just some notes though:
> 	(local_decimal_format_custom): Remove.
> 	
> 	* utils.c: (int_string): New function.
I suspect that the the blank lines aren't needed - blank lines separate 
  commits rather than separate parts of the same commit - whichever.

>       functions.  We have to split this up into separate print
> -     statements because local_hex_string returns a local static
> +     statements because hex_string returns a local static

can you file a bug report - that pre-existing behavior is a recipe for 
desaster :-(

Makefile.in will eventually need an update.  If you want to do it 
there's a script (gdb_makefile.in) hanging off of the ari web page that 
you might find useful.  Fixing the file is obvious.

I suspect that the special Makefile rule for printcmd.o can be deleted - 
  something for later.   Ditto.

Again, thanks.  Now where were we with Ada.

Andrew



  reply	other threads:[~2004-09-11  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11  0:38 Paul Hilfinger
2004-09-11  2:03 ` Andrew Cagney [this message]
2004-09-11  2:40   ` Paul Hilfinger
2004-09-11  3:50     ` Daniel Jacobowitz
2004-09-12 15:53       ` Andrew Cagney
2004-09-11 10:29   ` Paul Hilfinger
2004-09-11 11:32     ` Eli Zaretskii

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=41425E6F.4050607@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@gnat.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