Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Nick Roberts <nickrob@snap.net.nz>,
	gdb-patches@sources.redhat.com,   Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch/MI] Implementation for break-catch command
Date: Mon, 02 Jun 2008 13:23:00 -0000	[thread overview]
Message-ID: <4843F425.90809@qnx.com> (raw)
In-Reply-To: <200806010914.22980.vladimir@codesourcery.com>

Vladimir Prus wrote:
> On Sunday 01 June 2008 03:40:06 Nick Roberts wrote:
>>
>> I think all these "breakpoints" should be changed to use observers.  This
>> seems to just add to the ugliness.
> 
> They definitely should.

Well then, what is the preferred way? I can tweak my patch to take your comments into consideration, but if a switch to observers is going to happen soon, then I guess the break-catch should get this new stuff right away? Implementing observer_notify for all the breakpoints would break the compatibility and require quite a bit of work on the testsuite side.

Either way, Vladimir, it's your call - let me know.


  reply	other threads:[~2008-06-02 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 20:59 Aleksandar Ristovski
2008-05-28 21:26 ` Vladimir Prus
2008-05-28 21:36   ` Aleksandar Ristovski
2008-05-28 23:10     ` Eli Zaretskii
2008-05-29 20:46       ` Aleksandar Ristovski
2008-05-29 20:52         ` Aleksandar Ristovski
     [not found] ` <200805312006.11811.vladimir@codesourcery.com>
     [not found]   ` <18497.57814.496794.333674@kahikatea.snap.net.nz>
2008-06-01  5:15     ` Vladimir Prus
2008-06-02 13:23       ` Aleksandar Ristovski [this message]
2008-06-02 14:40         ` Vladimir Prus
2008-06-02 16:06   ` Aleksandar Ristovski
2008-06-02 16:28     ` Vladimir Prus
2008-07-31 14:06       ` Aleksandar Ristovski

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=4843F425.90809@qnx.com \
    --to=aristovski@qnx.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.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