From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13313 invoked by alias); 4 Apr 2012 08:36:21 -0000 Received: (qmail 13220 invoked by uid 22791); 4 Apr 2012 08:36:20 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-vx0-f169.google.com (HELO mail-vx0-f169.google.com) (209.85.220.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 04 Apr 2012 08:36:07 +0000 Received: by vcbfk14 with SMTP id fk14so13893vcb.0 for ; Wed, 04 Apr 2012 01:36:06 -0700 (PDT) Received: by 10.220.38.200 with SMTP id c8mr7302242vce.28.1333528566633; Wed, 04 Apr 2012 01:36:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.227.193 with HTTP; Wed, 4 Apr 2012 01:35:45 -0700 (PDT) In-Reply-To: <09787EF419216C41A903FD14EE5506DD0313D12A21@AUSX7MCPC103.AMER.DELL.COM> References: <83r4z8eqoa.fsf@gnu.org> <87zkaxn9zf.fsf@fleche.redhat.com> <4F7AE9C6.7050708@redhat.com> <09787EF419216C41A903FD14EE5506DD0313D12A21@AUSX7MCPC103.AMER.DELL.COM> From: Kevin Pouget Date: Wed, 04 Apr 2012 08:36:00 -0000 Message-ID: Subject: Re: [PATCH] Add bp_location to Python interface To: Paul_Koning@dell.com Cc: pmuldoon@redhat.com, tromey@redhat.com, gdb-patches@sourceware.org, eliz@gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 2012-04/txt/msg00054.txt.bz2 On Tue, Apr 3, 2012 at 4:42 PM, wrote: >>... >>Though I suspect it does not really matter -- the user can quite easily t= urn a tuple into a list. =A0As for returning a tuple versus a list, again, = I guess it does not really matter; the tuple idiom was just my convention (= though with very large lists, the conversion to a tuple might be expensive). > > If you know the number of items, the API lets you create the tuple with t= hat size and fill it in item by item, so there isn't necessary a conversion= from list to tuple involved. > Hello, On Tue, Apr 3, 2012 at 4:42 PM, wrote: > If you know the number of items, the API lets you create the tuple with t= hat size > and fill it in item by item, so there isn't necessary a conversion from l= ist to tuple > involved. the sequence size is not "known in advance", although it can be computed to instantiate the tuple before populating it; On Tue, Apr 3, 2012 at 2:15 PM, Phil Muldoon wrote: > though with very large lists, the conversion to a tuple might be expensive here [I think that] the list size is limited by the number of program spaces, which is usually the number of inferiors, so this conversion can't really be that expensive I'll wait for Tom's point of view before updating the code. (I'll also add the missing space in the doc in the next patch >> the following attributes (all read only). Breakpoint location ... ) thanks for your advises, Kevin