[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] minor additons to ICommandLauncher interface
|
That is a good point. I will look at doing that.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
![Inactive hide details for "Schorn, Markus" <Markus.Schorn@xxxxxxxxxxxxx>]()
"Schorn, Markus" <Markus.Schorn@xxxxxxxxxxxxx>
"Schorn, Markus" <Markus.Schorn@xxxxxxxxxxxxx>
04/23/2009 04:20 AM
|
|
Hi,
Because the API allows to implement ICommandLauncher in a future version any addition will be a non-compatible API change. So it would be wise to use an abstract class (where extensions are binary compatible) instead or forbid implementing the interface.
Markus.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Chris Recoskie
Sent: Monday, April 20, 2009 11:08 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] minor additons to ICommandLauncher interface
Importance: Low
I have to make some minor additons to the new ICommandLauncher interface I added for M6 in order to get the RDT remote managed builder working. Since ICommandLauncher is not yet a fully released API, there is no issue with breaking existing clients, but we are past the freeze so I thought I would give folks a heads up.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=272986 for details.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
