From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints
Date: Fri, 15 Feb 2002 18:28:00 -0000 [thread overview]
Message-ID: <20020215212853.A16436@nevyn.them.org> (raw)
In-Reply-To: <200202160050.g1G0o5Q04148@duracef.shout.net>
On Fri, Feb 15, 2002 at 06:50:05PM -0600, Michael Elizabeth Chastain wrote:
> This patch is declined for now, because I believe there is still controversy
> about the right thing to do for overloaded constructors and destructors.
>
> (And I am a party to that controversy ... so someone admonish please me if
> I start getting thickheaded).
Let me clarify terminology, please.
The patch tests _overloaded_ constructors. The bug, however, is with
_cloned_ constructors. Not the same thing at all. Cloned constructors
are not user-visible objects; they only differ in that they use
different offsets into the object based on whether it is a baseclass or
the principal object.
The test should definitely pass as-written, in my opinion, possibly
with a few additional words added to the output but not with more menu
choices. This is an implementation detail that we may want to show to
users but we should avoid requiring their knowledge of it at all
possible.
>
> Michael C
>
> ===
>
> 2002-02-14 Daniel Jacobowitz <drow@mvista.com>
>
> * gdb.c++/ovldbreak.exp: Test breakpoints on the constructors.
>
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-16 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 16:50 Michael Elizabeth Chastain
2002-02-15 18:28 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 16:04 Michael Elizabeth Chastain
2002-02-19 16:12 ` Daniel Jacobowitz
2002-02-18 12:26 Michael Elizabeth Chastain
2002-02-18 13:17 ` Daniel Jacobowitz
2002-02-19 15:35 ` Daniel Jacobowitz
2002-02-16 11:11 Michael Elizabeth Chastain
2002-02-14 15:32 Daniel Jacobowitz
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=20020215212853.A16436@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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