From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI varobj properties
Date: Wed, 15 Nov 2006 21:02:00 -0000 [thread overview]
Message-ID: <17755.32622.609016.534114@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200611151942.14091.vladimir@codesourcery.com>
> Except for getting the value of a variable objects, all those properties are
> computed by gdb, and there are no complex algorithms. How about the
> following change:
>
>
> - The commands that create new variable object always return full
> list of properties.
> - There's a new command that also returns the full list of properties
> - For backward compatibility, existing commands just forward
> to the new command.
>
> Comments?
I only use the properties currently output with -var-create. I think first you
need to consider carefully how you would use any new command and which
properties change after creation (if there are none then they could all be
accessed from -var-create). I'm not sure what you mean by forward to the new
command, presumably you can add a new command and leave the old ones as they
are.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2006-11-15 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 16:42 Vladimir Prus
2006-11-15 17:48 ` Jim Ingham
2006-11-15 21:02 ` Nick Roberts [this message]
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=17755.32622.609016.534114@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@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