Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Michael Snyder <msnyder@specifix.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org,
		Joel Brobecker <brobecker@adacore.com>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] 09/10 Add "continue --all"
Date: Mon, 19 May 2008 22:46:00 -0000	[thread overview]
Message-ID: <je7idqqgcw.fsf@sykes.suse.de> (raw)
In-Reply-To: <20080519182537.GA21992@caradoc.them.org> (Daniel Jacobowitz's 	message of "Mon, 19 May 2008 14:25:37 -0400")

Daniel Jacobowitz <drow@false.org> writes:

> On Mon, May 19, 2008 at 11:19:42AM -0700, Michael Snyder wrote:
>> What about "continue /all"?  More in keeping with the
>> argument syntax of existing gdb commands (print, examine...)
>
> So far there are only single letter specifiers, and they're all output
> formats (print/x, disassemble/m).  Adding multi-letter ones
> would be pretty confusing, IMO.
>
> If we want functionality arguments, especially multi-letter ones, I
> have a small preference for --all.

IMHO the best fit in the current cli syntax would be a subcommand.  Any
ambiguity can be resolved the same way as `set variable'.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


      reply	other threads:[~2008-05-19 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 18:12 Pedro Alves
2008-05-07 11:58 ` Pierre Muller
2008-05-07 19:36   ` Pedro Alves
2008-05-08 18:29 ` Eli Zaretskii
2008-05-09  2:35   ` Pedro Alves
2008-05-09  3:08     ` Daniel Jacobowitz
2008-05-09  3:54       ` Pedro Alves
2008-05-09 17:07         ` Pedro Alves
2008-05-09 19:08           ` Daniel Jacobowitz
2008-05-09 19:20             ` Andrew STUBBS
2008-05-11 20:34             ` Joel Brobecker
2008-05-19 17:07               ` Pedro Alves
2008-05-19 21:29                 ` Michael Snyder
2008-05-19 21:55                   ` Daniel Jacobowitz
2008-05-19 22:46                     ` Andreas Schwab [this message]

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=je7idqqgcw.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@specifix.com \
    --cc=pedro@codesourcery.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