From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29022 invoked by alias); 21 Jun 2012 20:38:02 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 28967 invoked by uid 22791); 21 Jun 2012 20:38:01 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Tom Tromey To: Keith Seitz Cc: archer@sourceware.org Subject: Re: Explicit Linespecs Branch Created References: <4FD6548D.3050701@redhat.com> <87haucs9yo.fsf@fleche.redhat.com> <4FE37137.7000408@redhat.com> Date: Thu, 21 Jun 2012 20:38:00 -0000 In-Reply-To: <4FE37137.7000408@redhat.com> (Keith Seitz's message of "Thu, 21 Jun 2012 12:08:39 -0700") Message-ID: <8762akl7tz.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2012-q2/txt/msg00003.txt.bz2 Keith> IOW, I am/was trying to avoid implementing backend gdb APIs in terms Keith> of the command line. I see. Well, that does make sense. It just seems like it will be hard to use from the CLI. Tom> How hard is it to add support for this to other linespec-using Tom> commands? Keith> That all depends on the UI. For the CLI, the relevant bits of code Keith> could be put into a separate function trivially enough. I didn't do Keith> that this round because I was not planning to add this feature to Keith> anything more than break_command. [list_command would be a follow-on Keith> feature addition.] But I'll do that before submitting again. FWIW I'd rather get the first bits in than delay the patch for a new feature. It's easy enough to do follow-ups, and they're easier to review besides. Tom