This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Another proposal for frontends and queries.


> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Hui Zhu
> Sent: Wednesday, September 16, 2009 2:25 AM
> To: Joel Brobecker
> Cc: gdb-patches@sourceware.org; Marc Khouzam; Michael Snyder
> Subject: Re: Another proposal for frontends and queries.
> 
> On Wed, Sep 16, 2009 at 00:26, Joel Brobecker 
> <brobecker@adacore.com> wrote:
> > Marc, Hui,
> >
> >> > I think we should scrap out nquery from record.c, 
> turning those to
> >> > query's, 'error's or normal stops, appropriately. ?What 
> would be missed?
> >
> > Branch time is very soon, but such a change would be acceptable on
> > the branch too. I just want to make sure that we reach a 
> solution before
> > the 7.0 release, and preferably before the first pre-release, which
> > should be a day or two after the branch.
> >
> > Hui, would you agree with changing the nquery calls into 
> calls to query?
> 
> Sorry I didn't follow this thread very clear.
> 
> We really need to do it?  I think add a switch (Like Marc did) or fix
> the nquery is better.

I guess the question that has come up is: is it very important to use
nquery() in PReccord instead of query()?  If we simply use query() then
PRecord will work well with Eclipse (and maybe other frontends).
The user should be smart enough to understand what the query means and
should do just fine with ("y or n") instead of ("y or [n]")

Having that "[n]" seems of less value than getting PRecord to work with
Frontends, no?

Thanks

Marc


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]