Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sources.redhat.com
Subject: Re: Variable objects and STL containers
Date: Mon, 11 Feb 2008 13:07:00 -0000	[thread overview]
Message-ID: <20080211130636.GA7796@caradoc.them.org> (raw)
In-Reply-To: <200802111211.36848.ghost@cs.msu.su>

On Mon, Feb 11, 2008 at 12:11:36PM +0300, Vladimir Prus wrote:
> I think that likewise, -var-update should create varobjs for new children,
> and return them -- we probably need a new attribute to indicate that a varobj
> was just created. This might sound like breaking frontends not prepared to see
> new varobjs in -var-update output. However, this dynamic child behaviour will
> happen only as result of explicit request from frontend. It's natural to
> give frontend a choice between 'raw' representation and 'pretty' representation,
> and for compatibility, it's best to default to 'raw'. And if frontend asks
> gdb to use pretty representation for a varobj, or all varobj of given type,
> we can expect the frontend to property handle auto-created varobjs.

I suggest we wait until you have something implemented, and then see
how various front ends (emacs, kdevelop, Eclipse) react to it.  If
they break, we can limit the new behavior to mi3.

I want to finish up the quoting changes I discussed last year for mi3,
too...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-02-11 13:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  6:01 Nick Roberts
2008-02-05  6:17 ` Vladimir Prus
2008-02-05  6:34   ` Nick Roberts
2008-02-05  6:56     ` Vladimir Prus
2008-02-05 13:16     ` Daniel Jacobowitz
2008-02-15  9:24       ` Nick Roberts
2008-02-17  0:19         ` Nick Roberts
2008-02-17  7:14           ` Vladimir Prus
2008-02-17 19:55             ` Nick Roberts
2008-02-18  8:12               ` Vladimir Prus
2008-02-19 16:31         ` Daniel Jacobowitz
2008-02-05 11:31   ` Mark Kettenis
2008-02-05 12:03     ` Vladimir Prus
2008-02-05 13:18     ` Daniel Jacobowitz
2008-02-08  0:53   ` Nick Roberts
2008-02-08  6:47     ` Vladimir Prus
2008-02-10  4:28       ` Nick Roberts
2008-02-10  7:11         ` Vladimir Prus
2008-02-10 17:52           ` Daniel Jacobowitz
2008-02-10 18:14             ` Vladimir Prus
2008-02-10 19:45             ` Doug Evans
2008-02-10 19:44           ` Doug Evans
2008-02-10 20:05             ` Vladimir Prus
2008-02-10 21:02           ` Nick Roberts
2008-02-11  9:12             ` Vladimir Prus
2008-02-11 13:07               ` Daniel Jacobowitz [this message]
2008-02-11 20: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=20080211130636.GA7796@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --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