This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add bp_location to Python interface
- From: Kevin Pouget <kevin dot pouget at gmail dot com>
- To: gdb-patches at sourceware dot org
- Cc: pmuldoon at redhat dot com, tromey at redhat dot com, eliz at gnu dot org, Paul_Koning at dell dot com
- Date: Wed, 9 May 2012 09:18:16 +0200
- Subject: Re: [PATCH] Add bp_location to Python interface
- References: <CAPftXUL7Gag8pOzh6NF2t=nowBgSYa_Je3CkMQHgxexrNz+OHg@mail.gmail.com> <m3liqn9lym.fsf@redhat.com> <CAPftXULeNBNLT=9EixD3sEdtxcLkRuUFY6ny=2k9NSUQqHf+Bg@mail.gmail.com> <m3k4656dkx.fsf@redhat.com> <CAPftXU+NjNead1ZHEc8_P84py3esmOnAKVa2Y1KpxKX_augKsw@mail.gmail.com> <CAPftXUL6KTe-WEFnWR38pVnGUJhmEQgZ0J7R7heeR3GHtmrf5g@mail.gmail.com> <83r4z8eqoa.fsf@gnu.org> <CAPftXULwT9pTagJOzVsDjtdFkcoFwTWm3gs0=a=EYzMbZYHPgA@mail.gmail.com> <CADPb22Sj1SmW0u+usg6FfmrteOuv7inQWgd8YqxdMCuaH=KHdg@mail.gmail.com> <CAPftXU+R6kZqwF0ZFhc_dBQW54z__581rgLgbift3DcGLcCLhA@mail.gmail.com> <CADPb22RTZmwQ3VsrYYw--o=qUp+3_FOT6Sx6BU5dkcP9uGKmkw@mail.gmail.com> <CAPftXUJuT+m1G+9UGkzPpzo=rps2RMxXZkDVnUh17i9-G3YYgw@mail.gmail.com> <87zkaxn9zf.fsf@fleche.redhat.com> <CAPftXUJ4VqDsadmWYZ39qpyGd7UAV1G3iHkDkWkVKqyxGnSCqg@mail.gmail.com> <4F7AE9C6.7050708@redhat.com> <09787EF419216C41A903FD14EE5506DD0313D12A21@AUSX7MCPC103.AMER.DELL.COM> <CAPftXUL9HdnSMvdFVxG3Gn9GV8krwr8X07wYZDaZbpj=M856yw@mail.gmail.com>
On Wed, Apr 4, 2012 at 10:35 AM, Kevin Pouget <kevin.pouget@gmail.com> wrote:
>
> On Tue, Apr 3, 2012 at 4:42 PM, ?<Paul_Koning@dell.com> wrote:
> >>...
> >>Though I suspect it does not really matter -- the user can quite easily turn a tuple into a list. ?As 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 that 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, ?<Paul_Koning@dell.com> wrote:
> > If you know the number of items, the API lets you create the tuple with that size
> > and fill it in item by item, so there isn't necessary a conversion from list 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 <pmuldoon@redhat.com> 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
gentle remainder
thanks;
Kevin