Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: 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 21:29:00 -0000	[thread overview]
Message-ID: <1211221182.3601.9.camel@localhost.localdomain> (raw)
In-Reply-To: <200805191620.23279.pedro@codesourcery.com>

On Mon, 2008-05-19 at 16:20 +0100, Pedro Alves wrote:
> A Sunday 11 May 2008 17:00:01, Joel Brobecker wrote:
> > > If you don't like the all prefix then we can go back to continue
> > > --all, or even just continue all.  Continue takes a numeric argument
> > > and all will not conflict.
> >
> 
> I hadn't proposed continue all, because we evaluate the integer
> as an expression, so that prevents the highly dubious
> valued form of using the contents of a variable named "all" in
> the inferior with "continue all".  

This is a very valid concern.  Can't have ambiguity.

What about "continue /all"?  More in keeping with the
argument syntax of existing gdb commands (print, examine...)



  reply	other threads:[~2008-05-19 18:20 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 [this message]
2008-05-19 21:55                   ` Daniel Jacobowitz
2008-05-19 22:46                     ` Andreas Schwab

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=1211221182.3601.9.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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