Bug 357013 - it would be nice to express != constraints in annotation value matching
Summary: it would be nice to express != constraints in annotation value matching
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: 1.6.12   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-07 17:28 EDT by Andrew Clement CLA
Modified: 2011-09-08 11:48 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 Andrew Clement CLA 2011-09-07 17:28:29 EDT 
This would be nice:

get(@Anno(value!=5) * *)

which would match gets of fields i and k here:

@Anno(value=4)
int i

@Anno(value=5)
int j

@Anno(value=6)
int k
Comment 1 Andrew Clement CLA 2011-09-08 11:48:11 EDT 
implemented.  In order to not create problems with changing the serialized form, the internal structures suffix the key name with a '!' when a != check is being made.