RE: Another proposal for frontends and queries.

[Marc Khouzam <marc.khouzam@ericsson.com>]

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: September-14-09 2:42 AM
> To: gdb-patches@sources.redhat.com
> Subject: Re: Another proposal for frontends and queries.
> 
> Marc Khouzam wrote:
> 
> > Hi,
> > 
> > I'm starting a new thread in an attempt to get this issue 
> resolved before 7.0.
> > 
> > Three-line recap of the issue:
> > 
> > For some frontends queries are answered automatically by GDB.
> > Because of this, some actions that the frontends wants to trigger
> > are automatically cancelled by GDB.
> ...
> > My latest idea, based on the reactions to the previous suggestions
> > is to extend "set confirm" and add a new "force" option.
> > set confirm on/off would remain as before
> > set confirm force would automatically answer 'y' to all queries.
> 
> So, the current problem is that some queries for which the frontend
> wants implicit 'yes' are answered as 'no'. You propose an option to
> make all queries answered as 'yes'. What if frontend wants some query
> answered as 'no'? 

Currently, all queries use 'y' to mean "perform action" and 'n' to mean
"cancel action".  Therefore, if a frontend does not want an action
performed, it should simply not send the command that will trigger
the action/query.  So, currently, there is no reason for a frontend
to want to force a 'n' to a query.
In the future, if this case does come up, we will need a specific
option for such a new query, kind of like "show/set breakpoint pending".

But I'm open to a new suggestion.

Thanks,
Marc