Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Bug fixes for CLI "show" command
Date: Wed, 21 Apr 2004 19:26:00 -0000	[thread overview]
Message-ID: <4086CAEE.6090807@gnu.org> (raw)
In-Reply-To: <3405-Wed21Apr2004213810+0300-eliz@gnu.org>

>>>> > 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!
> 
> 
> FWIW, I think we should not introduce new i18n problems, even though
> we don't actively work on adding i18n support at this time.

Yep.  We've even got some i18n patches submitted (why I created the i18n 
category in the bug database).

The only interface that needs reworking is add_setshow_cmd.  The old 
code (using add_set_cmd and add_set_from_show) can be pushed to one side.

Andrew



  reply	other threads:[~2004-04-21 19:26 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
2004-04-21 18:39         ` Eli Zaretskii
2004-04-21 19:26           ` Andrew Cagney [this message]
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=4086CAEE.6090807@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=eliz@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