From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Bug fixes for CLI "show" command
Date: Wed, 21 Apr 2004 15:53:00 -0000 [thread overview]
Message-ID: <20040421155350.GA6885@nevyn.them.org> (raw)
In-Reply-To: <40869808.50409@gnu.org>
On Wed, Apr 21, 2004 at 11:49:28AM -0400, Andrew Cagney wrote:
> >On Tue, Apr 20, 2004 at 01:34:22PM -0400, Andrew Cagney wrote:
> >
> >>>>>- ui_out_field_string (uiout, "prefix", list->prefixname + 5);
> >>>>>- cmd_show_list (*list->prefixlist, from_tty, list->prefixname + 5);
> >>>>>+ char *new_prefix = strstr (list->prefixname, "show ") + 5;
> >>
> >>>
> >>>This is no better - i18n.
> >
> >
> >Well, "this is no better from an i18n perspective". That doesn't mean
> >it isn't better! I'm trying to solve the cosmetic bug, not clear the
> >road for later i18n, which will require changing all this anyway.
>
> If we touch any i18n breakage, we should fix it. Just like, if we break
> any deprecated code, we should fix it.
I am not interested in reworking the interface of widely used functions
to support i18n, when there is no comprehensive plan or anyone working
on i18n support for GDB. Is that really unreasonable? It's just
wasted work!
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-04-21 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 20:00 Daniel Jacobowitz
2004-04-21 14:55 ` Andrew Cagney
2004-04-21 14:59 ` Daniel Jacobowitz
2004-04-21 15:49 ` Andrew Cagney
2004-04-21 15:53 ` Daniel Jacobowitz [this message]
2004-04-21 18:39 ` Eli Zaretskii
2004-04-21 19:26 ` Andrew Cagney
2004-04-21 21:48 ` Jason Molenda
2004-04-21 22:22 ` Andrew Cagney
2004-05-10 18:17 ` 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=20040421155350.GA6885@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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