From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9439 invoked by alias); 22 Mar 2008 14:49:58 -0000 Received: (qmail 9431 invoked by uid 22791); 22 Mar 2008 14:49:57 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Mar 2008 14:49:34 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id EE90098118; Sat, 22 Mar 2008 14:49:32 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id C6F059801D; Sat, 22 Mar 2008 14:49:32 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Jd52J-000553-5q; Sat, 22 Mar 2008 10:49:31 -0400 Date: Sat, 22 Mar 2008 14:49:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Vladimir Prus , gdb-patches@sources.redhat.com Subject: Re: [RFA] Fix breakpoint condition that use member variables. Message-ID: <20080322144931.GA19219@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , Vladimir Prus , gdb-patches@sources.redhat.com References: <200803221240.16230.vladimir@codesourcery.com> <200803221536.07586.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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: 2008-03/txt/msg00334.txt.bz2 On Sat, Mar 22, 2008 at 02:55:42PM +0200, Eli Zaretskii wrote: > That could surprise the user. Is it possible to make an additional > change to look for possible other interpretations of i_ which are > currently in scope, and display a warning of some kind if such > possibilities are found? This is how breakpoint conditions have worked as long as I can remember: they are evaluated at the time the breakpoint is hit, not at the time they are typed. So whatever they reference has to be in scope then. The early parsing is mainly to give early warning if something doesn't parse. -- Daniel Jacobowitz CodeSourcery