public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Ian Lance Taylor <iant@google.com>, Frysk List <frysk@sourceware.org>
Subject: Re: Roadmap beginnings
Date: Mon, 14 Jul 2008 18:12:00 -0000	[thread overview]
Message-ID: <20080714181200.GA11562@caradoc.them.org> (raw)
In-Reply-To: <m3y7447373.fsf@fleche.redhat.com>

On Mon, Jul 14, 2008 at 12:04:00PM -0600, Tom Tromey wrote:
> I thought operator overloading did not work, but a simple test case
> shows that it actually does.  And, I can at least print elements of a
> std::vector<int> using "p v[3]", and "p *it" works for an iterator of
> this vector.

Yes.  Operator overloading works fine, as long as the available
overloads are relatively easy to locate and distinguish.  If they come
from different scopes or you start needing to make constructor calls
to convert, GDB will rapidly throw up its hands.  That's where we get
into the part of the G++ front end that's been described to me as
"about 10,000 lines to get right".

GDB doesn't know how to call constructors, either - it can't do "new".
That seems like it would be a more serious limitation, but I can't
think the last time I wanted to do it.  Anyway, a simple matter of
programming.

I think the discussion of GDB limitations is wandering a bit afield
for this conversation; I'll stop answering for a bit, and perhaps put
together a combined response or a wiki page with summary, later on.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2008-07-14 18:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 19:53 Tom Tromey
2008-07-11 20:56 ` Jan Kratochvil
2008-07-11 21:37   ` Tom Tromey
2008-07-11 21:54     ` Daniel Jacobowitz
2008-07-11 23:11   ` Kris Van Hees
2008-07-11 21:53 ` Daniel Jacobowitz
2008-07-14 16:34   ` Tom Tromey
2008-07-14 16:45     ` Daniel Jacobowitz
2008-07-14 16:58       ` Phil Muldoon
2008-07-14 17:09         ` Daniel Jacobowitz
2008-07-14 17:19     ` Ian Lance Taylor
2008-07-14 17:34       ` Daniel Jacobowitz
2008-07-14 18:04         ` Tom Tromey
2008-07-14 18:12           ` Daniel Jacobowitz [this message]
2008-07-14 18:11         ` Ian Lance Taylor
2008-07-14 17:35       ` Tom Tromey
2008-07-14 18:13         ` Ian Lance Taylor
2008-07-22 20:29   ` Debugger Work (Was: Roadmap beginnings) Tom Tromey
2008-07-11 22:48 ` Roadmap beginnings Phil Muldoon

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=20080714181200.GA11562@caradoc.them.org \
    --to=drow@false.org \
    --cc=frysk@sourceware.org \
    --cc=iant@google.com \
    --cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).