From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR python/11792
Date: Thu, 02 Sep 2010 10:32:00 -0000 [thread overview]
Message-ID: <83zkw0j15r.fsf@gnu.org> (raw)
In-Reply-To: <m3wrr58501.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 01 Sep 2010 16:37:34 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Tom> The current language doesn't matter; all that matters is whether the
> Tom> object has the needed run-time type information.
>
> Eli> Then IMO the text should be rephrased, because it currently sounds
> Eli> like this feature needs C++. Perhaps use C++ just "for example" or
> Eli> something.
>
> I think that would be more confusing. The information needed is
> specifically that emitted by the C++ compiler, following the relevant
> C++ ABI. "For example" makes it sound as though other kinds of run-time
> type information might be used -- but that is not the case.
Now I'm confused: earlier you told that the current language doesn't
matter, but now you say that only information emitted by the C++
compiler will do, which seems a contradiction. What am I missing?
next prev parent reply other threads:[~2010-09-02 3:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 20:13 Tom Tromey
2010-08-30 18:01 ` Tom Tromey
2010-08-30 18:24 ` Eli Zaretskii
2010-08-30 20:24 ` Tom Tromey
2010-08-30 20:43 ` Eli Zaretskii
2010-09-01 23:01 ` Tom Tromey
2010-09-02 10:32 ` Eli Zaretskii [this message]
2010-09-02 15:48 ` Tom Tromey
2010-09-02 18:40 ` Eli Zaretskii
2010-09-07 21:01 ` Tom Tromey
2010-09-22 16:33 ` Eli Zaretskii
2010-09-22 18:47 ` Tom Tromey
2010-09-22 19:15 ` Eli Zaretskii
2010-09-22 19:17 ` Joel Brobecker
2010-09-22 19:19 ` Eli Zaretskii
2010-09-22 19:26 ` Tom Tromey
2010-09-22 19:59 ` Eli Zaretskii
2010-09-22 20:57 ` Tom Tromey
2010-09-23 12:42 ` Eli Zaretskii
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=83zkw0j15r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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