Re: [RFC] 09/10 Add "continue --all"

[Pedro Alves <pedro@codesourcery.com>]

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".  "thread apply n" has the same
issue, so I realized that it's a moot concern.  :-)

> FWIW, I like "continue all", but I think I prefer the "all" prefix.
> I would probably have "all continue" be its own command rather
> than having it an alias of "thread apply all continue" for the
> reasons that Pedro mentioned, and it shouldn't be much more work than
> the solution based on command aliasing.
>
> Using the "all" command prefix would be very elegant when we add
> more commands.  This assumes that there are other commands that
> we'd like to provide under that same prefix.

I'm still not sure.  Will we allow later to do things like:

'continue -t 4' -> continue thread 1, even though I have selected
thread 1.

Which would be the same as -exec-continue --thread="4".

?

'continue -a' feels like an extension to that.

OTOH, Should we have "thread apply all stopped do_x",
and "thread apply all all running" instead?
Could be aliased to allr, alls, for example.

-- 
Pedro Alves