Re: [cdt-dev] Addition of Mach-O 64 Binary Parser to 6.0.2

["Christian W. Damus" <cdamus@xxxxxxx>]

Hi, John,

Yes, I think I have the same understanding as you.  There is nothing that I know of that makes it infeasible for a willing client to require a service-level version of another plug-in with the knowledge that it provides new non-breaking API.  This is almost certainly a perfectly harmless case in which that would work.

I think that a few years of being responsible for the release process of a few modeling project components with many dependents has bludgeoned the "rules" into my brain to the point where it no longer perceives the colour grey.  :-D

cW

On Tue, 2009-11-03 at 14:02 -0600, John Cortell wrote:
>     Fair enough. So the "restriction" is really just rooted in convention and expectations. And that's fair enough. I guess I'm just trying to validate my understanding that there's no hard technical hurdle preventing a supplier bundle from adding API and a client from using it. The new API doesn't break clients, and it doesn't require clients to bump their dependency version bounds except for the few (if any) that would use the API in that release.
>     
>     John
>     
>     At 01:47 PM 11/3/2009, Christian W. Damus wrote:

--------8<--------

---

Christian W. Damus
Software Developer, IDE Team
QNX Software Systems