Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] API breaking change in CDT debug

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
> Sent: March-15-10 4:41 PM
> To: CDT General developers list.; CDT General developers list.
> Subject: Re: [cdt-dev] API breaking change in CDT debug
> 
> At 01:49 PM 3/15/2010, Dave Korn wrote:
> >On 15/03/2010 16:33, John Cortell wrote:
> > > [This happened Friday, before the M6 build]
> > >
> > > Eventbreakpoint (gdb catchpoint) constants that were in 
> > > org.eclipse.cdt.debug.mi.core.cdi.model.EventBreakpoint have been 
> > > move to 
> org.eclipse.cdt.debug.core.model.ICEventBreakpoint, and many 
> > > have undergone name changes for consistency reasons
> >
> >   FTR, the API between the core platform and the CDT also changed:
> >IPresentationContext grew a 'getWindow()' method in 3.6M6 
> that wasn't 
> >there in M5.  So there's a pretty thorough break between M5 
> and M6 all round.
> 
> Adding a method to a public class/interface doesn't break the API. 

It does for an interface, no?
But in this case, the interface is internal, so they are allowed to
break it.  We're not supposed to be using it.

> The platform hasn't "officially" broken its API in about six 
> years (though they've broken things at the behavioral level). 
> Personally, I find that amazing. Says a lot about those 
> developers--how careful and forward-thinking they are in 
> developing their interfaces.

That is amazing.  And probably headache-inducing :-)

> 
> John 
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 

Back to the top