From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH:MI] Return a subset of a variable object's children
Date: Thu, 29 May 2008 12:01:00 -0000 [thread overview]
Message-ID: <18493.56145.992962.378470@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200805281122.52651.vladimir@codesourcery.com>
> I think that the current data structures surely allow to implement the
> behaviour that is useful for frontends. I raise some questions about the
> original version of your patch in
>
> http://article.gmane.org/gmane.comp.gdb.patches/40676
>
> which you did not respond to. Did you miss that email?
I think these question were addressed in subsequent e-mails.
1) I now post patches in unified diff format.
2) I explained why I thought the stride was useful, e.g.,
(http://sourceware.org/ml/gdb-patches/2008-04/msg00680.html)
3) I acknowledged that the children should be reported in order
(http://sourceware.org/ml/gdb-patches/2008-04/msg00675.html)
and my last patch did this using linked lists.
> Do you plan to have
> the original version of your patch adjusted and checked in?
No. I couldn't get it to report the additional children/update in the correct
order using vectors.
> For the record, the usecases that I think will benefit from this new
> functionality are outlined in:
>
> http://article.gmane.org/gmane.comp.gdb.patches/40726
I think the use cases are more extensive but I don't currently have any
user feedback to back up that assertion.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-05-28 22:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:34 Nick Roberts
2008-04-29 15:58 ` Marc Khouzam
2008-04-30 7:02 ` Nick Roberts
2008-04-30 9:20 ` Vladimir Prus
2008-04-30 9:25 ` Nick Roberts
2008-04-30 9:39 ` Vladimir Prus
2008-04-30 16:29 ` Marc Khouzam
2008-05-01 15:56 ` Vladimir Prus
2008-05-01 17:29 ` Marc Khouzam
2008-05-01 12:15 ` Nick Roberts
2008-05-10 14:45 ` Nick Roberts
2008-05-28 19:15 ` Vladimir Prus
2008-05-29 12:01 ` Nick Roberts [this message]
2008-04-30 16:22 ` Marc Khouzam
2008-05-01 15:54 ` Vladimir Prus
2008-05-01 18:14 ` Marc Khouzam
2008-05-01 18:40 ` Vladimir Prus
2008-05-01 20:49 ` Daniel Jacobowitz
2008-05-01 23:38 ` Nick Roberts
2008-05-02 0:58 ` Marc Khouzam
2008-05-11 17:45 ` Vladimir Prus
2008-04-30 10:47 ` André Pönitz
2008-04-30 12:20 ` Vladimir Prus
2008-04-30 12:53 ` André Pönitz
2008-04-30 13:11 ` Vladimir Prus
2008-04-30 12:44 ` Nick Roberts
[not found] ` <200804301244.55116.apoenitz@trolltech.com>
2008-04-30 13:16 ` André Pönitz
2008-05-01 6:27 ` Nick Roberts
2008-05-05 11:46 ` André Pönitz
2008-04-30 14:59 ` Marc Khouzam
2008-05-01 12:06 ` Nick Roberts
2008-05-01 14:22 ` Marc Khouzam
2008-05-01 20:41 ` Daniel Jacobowitz
2008-04-30 8:59 ` Vladimir Prus
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=18493.56145.992962.378470@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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