From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR 1535
Date: Thu, 14 Aug 2008 17:49:00 -0000 [thread overview]
Message-ID: <20080814174814.GB15804@caradoc.them.org> (raw)
In-Reply-To: <m3fxpa6igp.fsf@fleche.redhat.com>
On Tue, Aug 12, 2008 at 03:17:58PM -0600, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Tom> This patch fixes PR 1535.
> Tom> The bug here is that CLI tab completion does not work for "catch"
> Tom> commands.
>
> After sending this I noticed a gettext snafu in the
> DEFINE_UNIMPLEMENTED macro -- stringization can't reasonably work
> here.
>
> The fix is to change the error call to use %s instead.
>
> I ran 'make gdb.pot' and looked at the result to verify that this
> change worked.
Just my taste, but I think this is pretty ugly. Manually expanded
tables wouldn't be any better. I think it's not as much extra typing
as you'd think to do it all without the tables.
Something like this: add_catch_command which takes normal add_cmd-like
arguments and adds the command to both catch and tcatch. A single,
manually written "catch_unimplemented" for the unimplemented commands
- or just remove them, what value do they add? And the other
functions are pretty simple. Most of the bulk of TABLE is the
docstrings.
In other words, make it as much like other commands as possible.
WDYT?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-14 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 18:19 Tom Tromey
2008-08-12 21:18 ` Tom Tromey
2008-08-14 17:49 ` Daniel Jacobowitz [this message]
2008-08-14 18:00 ` Tom Tromey
2008-08-14 18:15 ` Tom Tromey
2008-08-14 23:24 ` Tom Tromey
2008-08-15 4:20 ` Daniel Jacobowitz
2008-08-15 8:44 ` Andreas Schwab
2008-08-17 17:40 ` 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=20080814174814.GB15804@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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