From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32380 invoked by alias); 23 Jan 2015 16:35:26 -0000 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 Received: (qmail 31742 invoked by uid 89); 23 Jan 2015 16:35:16 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout22.012.net.il Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 23 Jan 2015 16:35:12 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NIN00I001ZQ2000@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Fri, 23 Jan 2015 18:34:01 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NIN00ICS20O0Q10@a-mtaout22.012.net.il>; Fri, 23 Jan 2015 18:34:01 +0200 (IST) Date: Fri, 23 Jan 2015 16:49:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 3/3 v2] Implement completion limiting In-reply-to: To: Doug Evans Cc: gbenson@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83zj99sbgk.fsf@gnu.org> References: <1417094168-25868-1-git-send-email-gbenson@redhat.com> <1417094168-25868-4-git-send-email-gbenson@redhat.com> <20141210122233.GA7299@blade.nx> <21671.20308.262958.475080@ruffy2.mtv.corp.google.com> <20150107084255.GA17867@blade.nx> <21680.36641.315766.209208@ruffy2.mtv.corp.google.com> <83a91r6lbd.fsf@gnu.org> <20150115153930.GA14900@blade.nx> <83h9vhu7k8.fsf@gnu.org> X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00655.txt.bz2 > Date: Fri, 23 Jan 2015 08:14:15 -0800 > From: Doug Evans > Cc: Gary Benson , > "gdb-patches@sourceware.org" > > The patch stops searching when the limit is reached. > It doesn't keep looking for at least one more to see if there are any more. > Is this absolutely critical? Why? Because if the user sets the maximum at N, she wants to see N elements, and if there are exactly N, she shouldn't get any warnings, IMO.