From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4237 invoked by alias); 13 Oct 2010 16:07:39 -0000 Received: (qmail 4226 invoked by uid 22791); 13 Oct 2010 16:07:39 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 Oct 2010 16:07:34 +0000 Received: (qmail 2449 invoked from network); 13 Oct 2010 16:07:32 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 13 Oct 2010 16:07:32 -0000 Date: Wed, 13 Oct 2010 16:07:00 -0000 From: Daniel Jacobowitz To: Ken Werner Cc: Tom Tromey , Joel Brobecker , Ulrich Weigand , gdb-patches@sourceware.org Subject: Re: [patch] fix pre-/post- in-/decrement Message-ID: <20101013160729.GO8337@caradoc.them.org> References: <201010041301.o94D1QHV032611@d12av02.megacenter.de.ibm.com> <201010071438.00571.ken@linux.vnet.ibm.com> <201010131123.40225.ken@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201010131123.40225.ken@linux.vnet.ibm.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00223.txt.bz2 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