Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: Paul_Koning@dell.com
Cc: pmuldoon@redhat.com, tromey@redhat.com,
	gdb-patches@sourceware.org, 	eliz@gnu.org
Subject: Re: [PATCH] Add bp_location to Python interface
Date: Wed, 04 Apr 2012 08:36:00 -0000	[thread overview]
Message-ID: <CAPftXUL9HdnSMvdFVxG3Gn9GV8krwr8X07wYZDaZbpj=M856yw@mail.gmail.com> (raw)
In-Reply-To: <09787EF419216C41A903FD14EE5506DD0313D12A21@AUSX7MCPC103.AMER.DELL.COM>

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


  reply	other threads:[~2012-04-04  8:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 10:17 Kevin Pouget
2011-12-08 13:39 ` Phil Muldoon
2011-12-08 14:28   ` Kevin Pouget
2011-12-08 14:56 ` Phil Muldoon
2011-12-09 13:49   ` Kevin Pouget
2011-12-09 14:15     ` Phil Muldoon
2011-12-13 15:55       ` Kevin Pouget
2012-01-09 11:47         ` Kevin Pouget
2012-01-09 17:23           ` Eli Zaretskii
2012-01-10 15:09             ` Kevin Pouget
2012-01-10 16:03               ` Kevin Pouget
2012-01-10 17:25               ` Eli Zaretskii
2012-01-11 10:16                 ` Kevin Pouget
2012-01-11 10:27                   ` Eli Zaretskii
2012-01-10 22:24               ` Doug Evans
2012-01-11  9:05                 ` Kevin Pouget
2012-01-11 19:45                   ` Doug Evans
2012-01-27 13:04                     ` Kevin Pouget
2012-03-30 19:51                       ` Tom Tromey
2012-04-03 10:35                         ` Kevin Pouget
2012-04-03 12:15                           ` Phil Muldoon
2012-04-03 14:43                             ` Paul_Koning
2012-04-04  8:36                               ` Kevin Pouget [this message]
2012-05-09  7:18                                 ` Kevin Pouget
2012-04-05 16:27                           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPftXUL9HdnSMvdFVxG3Gn9GV8krwr8X07wYZDaZbpj=M856yw@mail.gmail.com' \
    --to=kevin.pouget@gmail.com \
    --cc=Paul_Koning@dell.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox