Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Jason Molenda <jmolenda@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC patch mi-cmds.c table format (pedantic)
Date: Fri, 19 Mar 2004 15:12:00 -0000	[thread overview]
Message-ID: <405B0DE9.50203@gnu.org> (raw)
In-Reply-To: <3489FABC-793D-11D8-A2F0-000393D457E2@apple.com>

> 
> On Mar 18, 2004, at 11:55 AM, Andrew Cagney wrote:
> 
>> First, have a look at:
>> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gdb&pr=496
> 
> 
> Ah, I hadn't seen that.
> 
> How do you envision the cli-mapped mi commands working (e.g. -gdb-set),  where files in the gdb/ directory are registering the commands?

There shouldn't be cli-mapped mi commands.  Both the MI and CLI should 
share a common framework.  However, in the mean time, I guess such a 
table should be pump-primed with all the cli-mapped mi entries.

> OK I'll come up with a real/tested patch.  The trailing initializers --  you don't mean this kind of change, do you?
> 
>>> -  { "exec-step", { NULL, 0 }, mi_cmd_exec_step},
>>> +  { "exec-step", { NULL, 0 }, mi_cmd_exec_step, NULL},
> 
> 
> I think you were talking about the final NULL entry.

Skip them as well, I don't see the benefit.

Andrew



  reply	other threads:[~2004-03-19 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Jason Molenda
2004-03-17 23:47 ` Jason Molenda
2004-03-19  0:09 ` Andrew Cagney
2004-03-19  0:34   ` Jason Molenda
2004-03-19 15:12     ` Andrew Cagney [this message]
2004-03-19  0:09 ` Eli Zaretskii
2004-03-18  5:53   ` Eli Zaretskii
2004-03-19  0:09   ` Jason Molenda
2004-03-18 19:26     ` Jason Molenda
2004-03-19 14:36     ` 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=405B0DE9.50203@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jmolenda@apple.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