From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8362 invoked by alias); 26 Aug 2011 01:41:05 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 8352 invoked by uid 22791); 26 Aug 2011 01:41:05 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Fri, 26 Aug 2011 01:41:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: Project Archer Subject: Re: [Archer] update on ambiguous linespec branch Message-ID: <20110826014046.GH2851@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2011-q3/txt/msg00004.txt.bz2 > * I didn't yet implement the new linespec types, namely allowing > "OBJFILE:" as a prefix, or "FILE:FUNCTION:LINE" or > "FILE:FUNCTION:LABEL". [...] > I don't think this item is really needed for the patch to go in. It > could be done as a follow-up, and IMO would be better that way, since > it will be a second huge change to linespec.c. On the practical side, I'm wondering how you are going to be able to implement the case where the user selects a sub-set of all matches without this part... For instance, if there are two functions called foobar, and the user types "break foobar", if he selects only to break on one of them (using the multiple choice menu), how are we going to support that without the linespec types above? Or are you thinking of adding support for that as a second step? -- Joel