Re: [MI] enabling non-stop mode

[Nick Roberts <nickrob at snap dot net dot nz>]

 > >  > Probably, we can extend this to enable feature that are not MI proper,
 > >  > say:
 > >  > 
 > >  > (gdb) -list-features
 > >  >         ^done,features=[....,"non-stop",....]
 > >  > (gdb) -enable-feature non-stop
 > >  > ^done
 > >  > 
 > >  > The only issue here is that non-stop mode availability in general
 > >  > depends on the target, so maybe we should have a separate commands
 > >  > to list "target" feature and then enable target features?
 > > 
 > > Why not just use -gdb-set?
 > > 
 > > maint set linux-async   -->  set linux-async  -->  -gdb-set linux-async
 > > maint set non-stop      -->  set  non-stop    -->  -gdb-set non-stop
 > 
 > This will now allow the frontend to check if non-stop mode is supported at
 > all.

I mean list "non-stop" as a feature, which AFAICS just outputting a string
field, _and_ do:

    add_setshow_boolean_cmd ("non-stop",...

I don't see the benefit of another MI command like -enable-feature and
that way non-stop mode can be more easily made available to CLI.

-- 
Nick                                           http://www.inet.net.nz/~nickrob