Re: [dsdp-tm-dev] Removing "implements" allowed for M4?

[David Dykstal <dykstal@xxxxxxx>]

Excellent point. I'll defer these until after M4 then.
---------------------------
Dave Dykstal
dykstal@xxxxxxx


On Dec 21, 2006, at 12:46 PM, Oberhuber, Martin wrote:

> Not 100% sure.
>
> If constants brought into the namespace of a class through
> "implements" are available to subclasses without qualification
> (and I'm pretty sure they are), then yes this would be an API
> breaking change.
>
> Because user code can inherit from RSE class A and then use
> the constants brought into A without qualification, whereas
> after the change it will need to qualify all those constants.
>
> Cheers,
> --
> Martin Oberhuber
> Wind River Systems, Inc.
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
>
> > -----Original Message-----
> > From: dsdp-tm-dev-bounces@xxxxxxxxxxx
> > [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of David Dykstal
> > Sent: Thursday, December 21, 2006 7:41 PM
> > To: Target Management developer discussions
> > Subject: [dsdp-tm-dev] Removing "implements" allowed for M4?
> >
> > There are several cases where RSE uses "implements <interface>" to
> > acquire access to constants. This is considered an archaic practice.
> > All constants should be explicitly referenced. Is fixing this
> > considered an API breaking change?
> > ---------------------------
> > Dave Dykstal
> > dykstal@xxxxxxx
> >
> >
> > _______________________________________________
> > dsdp-tm-dev mailing list
> > dsdp-tm-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev