Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sourceware.org
Subject: Re: Changes to varobj.c
Date: Thu, 29 May 2008 16:40:00 -0000	[thread overview]
Message-ID: <200805291154.23776.vladimir@codesourcery.com> (raw)
In-Reply-To: <18493.58735.890650.879225@kahikatea.snap.net.nz>

On Thursday 29 May 2008 03:06:23 Nick Roberts wrote:
> 
> I apologise if I missed it, but I never saw a patch for the change below.

I think you've missed it. The patch was posted here:

	http://article.gmane.org/gmane.comp.gdb.patches/40822

and the version I've checked in has no changes relative to the one
I've posted.

Would you like to CC-d on all MI patches?

> I can see a stale comment before varobj_update:
> 
>    NOTE: This function may delete the caller's varobj. If it
>    returns TYPE_CHANGED,...
> 
> (varobj_update no longer returns TYPE_CHANGED)

You are right. On the other hand, why do delete varobj when its
type changes, or in other words, why value_of_root uses varobj_create? I think
I'll just stop it making do so, together with the other planned change of
making -var-create of floating varobj not fail when the expression cannot be
parsed.

> If you want a second pair of eyes, I'm more likely to peer review patches than
> changes that have already been comitted

There are MI patches I'm fairly confident in, and there are patches where
a second pair of eye is appreciated. This one falls in the latter category,
and that's why I've posted it quite some time ago. I can CC you for all future
MI patches where comments are desired, or use [MI] prefix in emails, or something
else that will make sure you see them.

- Volodya


  parent reply	other threads:[~2008-05-29  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 14:40 Nick Roberts
2008-05-29 14:49 ` Daniel Jacobowitz
2008-05-29 16:40 ` Vladimir Prus [this message]
2008-05-29 16:46   ` Nick Roberts

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=200805291154.23776.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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