From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Eli Zaretskii <eliz@gnu.org>, Bob Rossi <bob@brasko.net>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH: gdb/mi + doco] -var-update
Date: Fri, 15 Jul 2005 04:16:00 -0000 [thread overview]
Message-ID: <20050715041538.GA29817@nevyn.them.org> (raw)
In-Reply-To: <17111.13428.966975.183852@farnswood.snap.net.nz>
On Fri, Jul 15, 2005 at 03:58:44PM +1200, Nick Roberts wrote:
> > This patch includes the missing files, and I redid the varobj change in
> > a pedantically different way. Thanks for catching my goof there, by
> > the way. And caught a bad argc check on -var-list-children that I
> > think you picked up from me at some point.
>
> Your change is clearly more object oriented. I don't know why varobj.c is in
> the gdb directory: it's only really used by mi-cmd-var.c. How about moving it
> into the mi directory, or even merging it with mi-cmd-var.c to form one file?
> That way all the static functions currently in varobj.c will be automatically
> accessible to the functions currently in mi-cmd-var.c.
I bet you've got only the GDB module checked out. Varobj was not
written for MI - it was written for Insight (gdb/gdbtk/).
> > How's it look? If it looks good to you, I'll check it in, and then you
> > can commit the documentation and we can work out what happened to your
> > testcase.
>
> Yes, it looks good to me. Perhaps I can test it more fully once you've
> committed it. Now that the hectic release schedule of GDB has slowed down, I
> think this is a good way to work. I'm not sure that you will agree, though.
In general, it's not my favorite approach, but it's growing on me. I
have checked in the patch now; feel free to check in the docs, since
Eli approved them. We can sort out testcases next.
BTW, if it's OK with you, I would prefer that you add new testcases
rather than modifying existing ones. Yes, the ones that are there are
slightly redundant. But changing what a test case is testing is bad
form for long-term results analysis.
> I think the behaviour should be governed by use not consistency. I don't
> really have an opinion though as I will only use:
Makes sense. I can see why displaying the type for -var-update seems
less than useful - although if it displayed dynamic type... hmmm...
well, something to think about much later.
Now that this patch is in, I believe your current gdb-mi.el will work
with CVS GDB. Is that right? If so, could you post it? I promise to
look at it promptly.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-15 4:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 2:06 Nick Roberts
2005-02-20 5:02 ` Eli Zaretskii
2005-02-20 5:51 ` Nick Roberts
2005-02-20 15:31 ` Eli Zaretskii
2005-02-21 4:33 ` Nick Roberts
2005-02-21 7:17 ` Eli Zaretskii
2005-02-22 9:23 ` Nick Roberts
2005-02-22 9:34 ` Eli Zaretskii
2005-02-27 5:03 ` Nick Roberts
2005-02-27 16:53 ` Eli Zaretskii
2005-02-27 16:56 ` Nick Roberts
2005-02-28 12:27 ` Eli Zaretskii
2005-03-19 3:55 ` Nick Roberts
2005-04-01 1:51 ` Bob Rossi
2005-04-01 11:01 ` Nick Roberts
2005-05-02 2:06 ` Nick Roberts
2005-05-02 4:05 ` Daniel Jacobowitz
2005-05-02 7:24 ` Nick Roberts
2005-06-17 3:43 ` Daniel Jacobowitz
2005-06-17 10:09 ` Eli Zaretskii
2005-06-17 14:04 ` Daniel Jacobowitz
2005-06-18 8:53 ` Eli Zaretskii
2005-07-03 19:56 ` Daniel Jacobowitz
2005-07-04 3:07 ` Nick Roberts
2005-07-04 3:51 ` Daniel Jacobowitz
2005-07-04 4:55 ` Eli Zaretskii
2005-07-04 5:02 ` Daniel Jacobowitz
2005-07-04 10:17 ` Nick Roberts
2005-07-06 10:00 ` Nick Roberts
2005-07-15 1:44 ` Daniel Jacobowitz
2005-07-15 3:59 ` Nick Roberts
2005-07-15 4:16 ` Daniel Jacobowitz [this message]
2005-07-15 15:11 ` Nick Roberts
2005-07-15 15:28 ` Daniel Jacobowitz
2005-07-15 22:37 ` Nick Roberts
2005-07-04 21:15 ` Nick Roberts
2005-07-04 22:24 ` Eli Zaretskii
2005-07-05 3:25 ` Nick Roberts
2005-07-05 19:37 ` Eli Zaretskii
2005-07-15 9:42 ` Nick Roberts
2005-06-17 11:42 ` Nick Roberts
2005-06-17 14:06 ` Daniel Jacobowitz
2005-06-17 23:12 ` Nick Roberts
2005-02-21 2:36 ` Andrew Cagney
2005-02-21 3:28 ` 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=20050715041538.GA29817@nevyn.them.org \
--to=drow@false.org \
--cc=bob@brasko.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--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