Bug 331075 - Resolved TypePattern nodes need to be tested for correctness
Summary: Resolved TypePattern nodes need to be tested for correctness
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-24 18:42 EST by Nieraj Singh CLA
Modified: 2010-11-24 18:42 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nieraj Singh CLA 2010-11-24 18:42:14 EST
Build Identifier: Eclipse 3.6 I20100608-0911


Although implementations for resolved TypePattern nodes like ExactTypePattern and BindingTypePattern nodes exist in both weaver and DOM ASTs, they are not covered by any unit tests, and consequently their implementation and conversion from weaver to DOM AST nodes have not been validated. The conversion occurs in AjASTConverter.

The converter only has been tested for WildTypePatterns, which only hold Type information as a String expression. 

Also, the getTypePatternExpression() in the DOM BindingTypePattern may be incorrect, as it concatenates the String representation of the Type with the binding. 

Reproducible: Always