Bug 225604 - [signals] Remove the empty ISignals interface definition
Summary: [signals] Remove the empty ISignals interface definition
Status: RESOLVED WONTFIX
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf (show other bugs)
Version: 0 DD 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: DD 1.0   Edit
Assignee: DD General Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2008-04-03 13:13 EDT by Pawel Piech CLA
Modified: 2009-01-07 17:06 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Piech CLA 2008-04-03 13:13:37 EDT 
DSF defines a ISignals interface which is meant to allows client to view and manage signals on the target.  However this interface is not yet implemented in DSF-GDB and it not even defined.  We should remove it and add it when needed after 1.0.
Comment 1 Pawel Piech CLA 2008-04-03 13:28:14 EDT 
I think I have to go back on my initial assessment.  The signals context defined in this interface is used by the MI plugins.  I think it's OK to leave this interface with the assumption that we'll have to expand this interface in near future.
Comment 2 Randy Rohrbach CLA 2008-04-04 09:21:50 EDT 
So if we leave it as is. When we do need the functionality we will be forced to wait until 2.0 to change it or we will have to create an ISignals2.java interface in a 1.1 release. This is pretty ugly.

Randy
Comment 3 Pawel Piech CLA 2008-04-04 14:02:52 EDT 
(In reply to comment #2)
Yes it is pretty ugly :-(.  But it is a pretty standard procedure for extending the interfaces, and it's better than defining an interface without a client or service implementation.