From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2975 invoked by alias); 4 Feb 2008 05:40:18 -0000 Received: (qmail 2344 invoked by uid 22791); 4 Feb 2008 05:40:09 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 04 Feb 2008 05:39:52 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D7C002AA3FB; Mon, 4 Feb 2008 00:39:50 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 790E21pFkKXX; Mon, 4 Feb 2008 00:39:50 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 92E642AA3F3; Mon, 4 Feb 2008 00:39:50 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 3A9D1E7ACB; Sun, 3 Feb 2008 21:39:47 -0800 (PST) Date: Mon, 04 Feb 2008 05:40:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFA] new set/show multiple-choice-auto-select command (take 3) Message-ID: <20080204053947.GD21614@adacore.com> References: <20080203043755.GI1581@adacore.com> <20080203204000.GB21614@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i 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-02/txt/msg00064.txt.bz2 > I'm uneasy about changing the default behavior, but perhaps this is > okay if breaking on overloaded methods was introduced not too long > ago. Is that the case? I don't think so (that it was he case). However, I think the new behavior is more useful in practice (from our experience in Ada at least), and the old behavior can be restored if some users are really attached to it. We actually made that change in behavior in the AdaCore version, and no complaints so far. Given all that, I think the change is for the better. The multiple-location breakpoint work already set the debugger in that direction, and this patch is another logical step towards it. I will make sure that the NEWS entry makes it clear that there is a change of behavior. -- Joel