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: [patch] fix pre-/post- in-/decrement

From: Daniel Jacobowitz <dan at codesourcery dot com>
To: Ken Werner <ken at linux dot vnet dot ibm dot com>
Cc: Tom Tromey <tromey at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, Ulrich Weigand <uweigand at de dot ibm dot com>, gdb-patches at sourceware dot org
Date: Wed, 13 Oct 2010 12:07:29 -0400
Subject: Re: [patch] fix pre-/post- in-/decrement
References: <201010041301.o94D1QHV032611@d12av02.megacenter.de.ibm.com> <201010071438.00571.ken@linux.vnet.ibm.com> <m3pqvff24r.fsf@fleche.redhat.com> <201010131123.40225.ken@linux.vnet.ibm.com>

On Wed, Oct 13, 2010 at 11:23:39AM +0200, Ken Werner wrote:
> On Wednesday, October 13, 2010 1:00:04 am Tom Tromey wrote:
> > While I don't really mind having language checks in the expression
> > evaluator, it seems like this particular error condition is something
> > that could be detected in the C parser.
> 
> Hmm interesting. I guess you are referring to c-exp.y as this generates the 
> expression parser for both languages C and C++. I don't see how to control the 
> type of the result of an operator there. I'm still quite new to the GDB 
> parsing internals and would appreciate any insights.

You could add an expression operator to remove lval-ness, for
instance.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Re: [patch] fix pre-/post- in-/decrement
  - From: Ulrich Weigand
- Re: [patch] fix pre-/post- in-/decrement
  - From: Ken Werner
- Re: [patch] fix pre-/post- in-/decrement
  - From: Tom Tromey
- Re: [patch] fix pre-/post- in-/decrement
  - From: Ken Werner

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