Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>,
	 gdb-patches@sources.redhat.com,  Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Implement -thread-info.
Date: Sun, 23 Mar 2008 07:38:00 -0000	[thread overview]
Message-ID: <200803231038.51044.vladimir@codesourcery.com> (raw)
In-Reply-To: <18405.58075.425704.501844@kahikatea.snap.net.nz>

On Sunday 23 March 2008 07:55:55 Nick Roberts wrote:
> Daniel Jacobowitz writes:
>  > On Tue, Feb 26, 2008 at 01:53:16PM +1300, Nick Roberts wrote:
>  > > +   { "thread-info", { "info threads", 1 }, NULL, NULL },
>  >
>  > I would suggest against using args_p == 1 for any new commands. 
>  > The quoting rules between CLI and MI are different; we ignore that
>  > for some commands, but it's a bug and it bites frontend
>  > developers.
>  >
>  > If the arguments are just going to be integers then it doesn't
>  > make much difference but it will make things simpler if we want to
>  > add either quoted arguments or dashed options later.
>
> With non-stop mode there will presumably be many new MI commands.

Just one, I think -- to enable non-stop mode. Many commands will take
additional options, though.

> Providing the same functionality in CLI duplicates a lot of effort. 
> Perhaps the parsing of MI and CLI arguments should be unified.

Are you suggesting that we continue to implement MI commands by
basically executing the corresponding CLI command? 

- Volodya




  reply	other threads:[~2008-03-23  7:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 15:33 Vladimir Prus
2008-02-18  6:26 ` Nick Roberts
2008-02-18  7:38   ` Vladimir Prus
2008-02-18 21:45     ` Nick Roberts
2008-02-20 11:28       ` Vladimir Prus
2008-02-20 19:07         ` Eli Zaretskii
2008-02-20 19:38         ` Nick Roberts
2008-02-20 20:03           ` Vladimir Prus
2008-02-26  0:58         ` Nick Roberts
2008-02-26  1:21           ` Daniel Jacobowitz
2008-03-23  4:56             ` Nick Roberts
2008-03-23  7:38               ` Vladimir Prus [this message]
2008-03-23 16:22               ` Daniel Jacobowitz
2008-03-08 15:50           ` Vladimir Prus
2008-03-08 15:55         ` Vladimir Prus
2008-03-08 20:04           ` Nick Roberts
2008-03-10  7:59             ` Vladimir Prus
2008-03-10  9:13               ` Nick Roberts
2008-03-14 10:17           ` Vladimir Prus
2008-03-17 18:40             ` Michael Snyder
2008-03-14 15:08           ` Daniel Jacobowitz
2008-03-14 15:11             ` Daniel Jacobowitz
2008-03-14 17:04               ` Vladimir Prus
2008-03-14 18:04                 ` 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=200803231038.51044.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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