Bug 83631 - @AJ and @Aspect
Summary: @AJ and @Aspect
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-25 12:04 EST by Alexandre Vasseur CLA
Modified: 2005-04-27 03:45 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Vasseur CLA 2005-01-25 12:04:50 EST 
discussion about the @Aspect

 @Aspect(instantiationModel=AspectInstantiationModel.PERTHIS,
             perClausePattern="execution(* abc..*(..))")

I find that one very verbose.

Wouldn't
  @Aspect("perthis(execution(* abc..*(..)))")
be enough and no enum at all
it only needs a startWith check and allow us to use the @Aspect with no enum
which is easier  for the java 1.4 doclet style as well.
Comment 1 Andrew Clement CLA 2005-01-25 12:16:44 EST 
I believe one argument for the strongly typed variant using enums is code
completion for annotations in the various tools would allow you to see the
possible per variants as you were typing, rather than trying to guess them. 
However, at least in AJDT we could probably get the same kind of code assist via
templates and use Alex's short form...
Comment 2 Alexandre Vasseur CLA 2005-04-27 03:45:40 EDT 
closing
We have a "String" driven annotation model to keep it simple, loosely tied to
any API that would implie some complex versionning etc, and not too much Java 5
things for (later) backport175 use.

Currently integrated in both weaver and compiler as String ie 
@Aspect("perClauseX(..pcd..)")