From: Cyrille Comar <comar@adacore.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Paul Koning <pkoning@equallogic.com>,
hilfingr@gnat.com, gdb@sourceware.org
Subject: Re: : Re: [RFC] multiple breakpoints from FILE:LINE
Date: Mon, 16 Jan 2006 14:16:00 -0000 [thread overview]
Message-ID: <43CBAAA2.2060009@adacore.com> (raw)
In-Reply-To: <20060116134731.GB31547@nevyn.them.org>
Daniel Jacobowitz wrote:
> No, you either use Class::Class or Class::~Class,
ok so this is not strictly the topic as decribed in the subject line.
Does it make more sense to widen the topic to include overloading and
implicit operations and more generally any multiple-breakpoints-at-once
issues or is it better to stick to the cases covered by the subject
line? That would cover inlining, C++ templates, Ada generics, C include
files.
It seems that each situation is relatively specific. At least, there
seem to be 2 different categories:
- inlining & constructors : where it has been advocated that a
single break command should insert multiple breakpoints
- overloading, generics, templates, includes: where it has been
advocated that some kind of choice is needed.
next prev parent reply other threads:[~2006-01-16 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 1:51 Cyrille Comar
2006-01-15 16:33 ` Paul Koning
2006-01-15 16:45 ` Daniel Jacobowitz
2006-01-15 17:41 ` Robert Dewar
2006-01-15 22:23 ` Paul Koning
2006-01-16 13:43 ` Cyrille Comar
2006-01-16 13:47 ` Daniel Jacobowitz
2006-01-16 14:16 ` Cyrille Comar [this message]
2006-01-16 15:31 ` Paul Koning
2006-01-15 17:38 ` Robert Dewar
2006-01-16 6:58 ` Jim Blandy
2006-01-16 10:03 ` Robert Dewar
2006-01-16 10:04 ` Robert Dewar
2006-01-15 22:23 ` Paul Hilfinger
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=43CBAAA2.2060009@adacore.com \
--to=comar@adacore.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=hilfingr@gnat.com \
--cc=pkoning@equallogic.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