Re: [aspectj-dev] AspectJ Custom Attributes

[Eduardo Rocha <eduardorochabr@xxxxxxxxx>]

Andy,

Actually it is not needed to change them into annotations, I would like to know it just to move on.

Thanks for reply!
Eduardo

2005/10/19, Andy Clement <andrew.clement@xxxxxxxxx>:

There is currently no plan to migrate our attributes to annotations.
We have introduced lots of new annotations in 1.5 to support features
like the @AJ syntax and the meta-aspect protocol (for example:
ajcDeclareEoW), but 'internal' attributes like
'MethodDeclarationLineNumber' are not going to become an annotation in
the 1.5 timeframe.  Attributes are valid entries in the class file, so
why would we need to change them into annotations?  If it is to make
them accessible by 'other tools' then I think the work we have done
creating new annotation types for the MAP support is good enough,
everything other tools should want to know about an aspect is in those
new annotation types - take a look in the
org.aspectj.internal.lang.annotation package...  It is a possible
future item to look into as it would externalize more clearly the form
of everything we put into a classfile...but I don't think it'll happen
soon.

Andy.

On 19/10/05, Eduardo Rocha <eduardorochabr@xxxxxxxxx> wrote:
> There is a thread in the ASM mailing list about AspectJ custom attributes,
> those contained in the class org.aspectj.weaver.AjAttribute:
>
>  http://www.objectweb.org/wws/arc/asm/2005-10/msg00006.html
>
>  Currently ASM doesn't support these attributes, since there is an
> expectation that these attributes get converted into common annotations.
>
>  So what AspectJ 1.5 final will bring? Keep these custom attributes or use
> common annotations?
>
>  Eduardo
>
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
>
>
_______________________________________________
aspectj-dev mailing list
aspectj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-dev