From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mec.gnu@mindspring.com, gdb@sources.redhat.com, rolandz@poczta.fm
Subject: Re: How to setup a breakpoint on constructor
Date: Fri, 16 Jul 2004 14:27:00 -0000 [thread overview]
Message-ID: <20040716142113.GB7311@nevyn.them.org> (raw)
In-Reply-To: <2914-Fri16Jul2004140923+0300-eliz@gnu.org>
On Fri, Jul 16, 2004 at 02:09:23PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 15 Jul 2004 09:54:28 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > FYI, I implemented this once. The users who tried it didn't like it at
> > all.
>
> Did they tell why they didn't like it?
(A) It was an ugly interface change to work around an internal
limitation, and they needed to retrain users to it.
(B) It exposes the difference between complete and base constructors,
which is an implementation detail of the C++ ABI that most users don't
understand.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-16 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 13:55 Michael Elizabeth Chastain
2004-07-15 14:09 ` Daniel Jacobowitz
2004-07-16 11:11 ` Eli Zaretskii
2004-07-16 14:27 ` Daniel Jacobowitz [this message]
2004-07-17 10:30 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 19:29 Michael Elizabeth Chastain
2004-07-19 3:58 ` Eli Zaretskii
2004-07-17 23:17 Michael Elizabeth Chastain
2004-07-18 5:05 ` Eli Zaretskii
2004-07-18 18:44 ` Daniel Jacobowitz
2004-07-18 19:03 ` Eli Zaretskii
2004-07-19 3:22 ` Daniel Jacobowitz
2004-07-19 14:51 ` Eli Zaretskii
2004-07-17 10:09 Michael Elizabeth Chastain
2004-07-16 19:59 Michael Elizabeth Chastain
2004-07-16 22:15 ` Jim Blandy
2004-07-17 14:30 ` Eli Zaretskii
2004-07-17 14:54 ` Daniel Jacobowitz
2004-07-15 11:31 Michael Elizabeth Chastain
2004-07-16 13:17 ` Roland Zerek
2004-07-15 10:30 Roland Zerek
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=20040716142113.GB7311@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=rolandz@poczta.fm \
/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).