Re: GNOME::Debugger::Commander proposal
- From: Martin Baulig <martin home-of-linux org>
- To: Dave Camp <campd oit edu>
- Cc: Elliot Lee <sopwith redhat com>, gnome-debugger-list gnome org
- Subject: Re: GNOME::Debugger::Commander proposal
- Date: 04 Oct 1999 19:44:51 +0200
Dave Camp <campd@oit.edu> writes:
> Dave Camp <campd@OIT.EDU> writes:
>
> > > > void set_breakpoint (in string file_name,
> > > > in long line_num,
> > > > in string condition);
> > > > void set_breakpoint_function (in string file_name,
> > > > in string function_name,
> > > > in string condition);
> > >
> > > These two should return the breakpoint #.
> > Most certainly.
>
> I'm sorry I take that back.
>
> 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.
Sorry for asking such silly questions, but ...
What's the big deal in making set/remove breakpoints asynchronous, normally
setting or removing a breakpoint isn't an "expensive" operation and thus
the call will normally immediately return to the caller with the breakpoint
set or removed.
Or do I miss something ?
--
Martin Baulig - martin@home-of-linux.org - http://www.home-of-linux.org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]