Re: GNOME::Debugger::Commander proposal
- From: Dave Camp <campd oit edu>
- To: Elliot Lee <sopwith redhat com>
- Cc: Martin Baulig <martin home-of-linux org>, gnome-debugger-list gnome org
- Subject: Re: GNOME::Debugger::Commander proposal
- Date: 03 Oct 1999 15:14:26 -0700
Elliot Lee <sopwith@redhat.com> writes:
> > We did this because this interface aims to be asynchronous. You will send
> > a set_breakpoint command, and at some point in the future, you will get
> > a "breakpoint set" event on the event channel.
>
> This is going to add a lot of complexity for no apparent reason.
There is a very good reason. There are a number of things that need to
be informed of an added breakpoint. The editor needs to know, so that it
can put up a breakpoint indicator. The breakpoint manager needs to know.
The one object that always knows when a breakpoint is added is the program
object. So it becomes the program object's responsibility to notify
interested components (via the event channel) that a breakpoint has been
added.
Cheers,
-dave
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]