Bug 103477 - methods that represent declare error/warning ITDs are never called
Summary: methods that represent declare error/warning ITDs are never called
Status: RESOLVED INVALID
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-12 08:28 EDT by Rafal Krzewski CLA
Modified: 2005-07-13 03:26 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 Rafal Krzewski CLA 2005-07-12 08:28:15 EDT 
... which is not a problem, but looks ugly in a test coverage tool output. You
can never get 100% coverage in a file that contains such an ITD :)

A way of fixing it would be making these methods static, and calling them from a
<clinit> block - unnoticable performance penalty, and only slight code size
increase.

I suspect that similar problem exists with other kinds of ITDs.
Comment 1 Rafal Krzewski CLA 2005-07-13 03:26:47 EDT 
After more thoguths, and reading helpful comments from Alexandre and Andy in Bug
Bug 103471, I decided that the best approach will be introducing a bit of
knowledge of AspectJ into the tool I am working on.

- small impact on the tool (basicly, if a method has
"org.eclipse.aspectj.AjSynthetic" attribute, don't instrument it)
- no change in AJ required
- claiming AspectJ compatiblitiy will be good marketing for Coverlipse ;)

resolving as INVALID - not an AJ bug.