Re: [aspectj-users] Possible AJ change: Read this if you use package (de

[Charles Zhang <zhangcharles@xxxxxxxxx>]

>From my (a user) point of view, our projects do find
package level visibility useful. That is, we introduce
methods or fields only visible in aspect packages.
They cannot be "pulic" since it will "leak" the
concern to the "outside". They cannot be private
because we want other non-child aspects in the same
package to know about them. So I vote "no" for making
it an error, if I didn't misunderstand the issue. 

Charles

--- Andy Clement <andrew.clement@xxxxxxxxx> wrote:

> There are a few bugs around to do with abstract ITDs
> that have package
> level visibility.  I mean something like:
> 
> abstract class A { }
> 
> aspect X {
>   abstract void A.foo();
> }
> 
> There is a lot of discussion about the problems they
> introduce in bug 72834:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=72834
> 
> I'm proposing to make it an error, depending on any
> feedback I get
> here, so that you can't 'specify' default visibility
> for abstract
> ITDs.
> 
> comments? use cases?
> 
> Andy.
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/aspectj-users
> 


Yawn !!