Bug 71113 - [1.5] improve DOM/AST specs for bindings for JLS3 constructs
Summary: [1.5] improve DOM/AST specs for bindings for JLS3 constructs
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.1 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-29 16:25 EDT by Jim des Rivieres CLA
Modified: 2005-01-11 11:02 EST (History)
1 user (show)

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 Jim des Rivieres CLA 2004-07-29 16:25:25 EDT 
The specs for ITypeBinding and IMethodBinding do not cover all the cases that 
need to be handled in JLS3. The particular area that the spec must cover are 
instances of generic type and generic methods.
Comment 1 Jim des Rivieres CLA 2004-07-29 16:38:34 EDT 
IBinding
- getKey() - added clauses in spec to cover new JLS3 bindings

ITypeBinding
- revised/clarified specs for various methods to explain how type bindings can 
arise from instances of generic types (parameterized type references and raw 
type references)
- clarified getTypeParameters() to say that these do not show up on the 
binding for instances of the generic type

IMethodBinding
- added isParameterizedMethod(), isRawMethod(), getErasure(), getTypeArgument()
- clarified specs for to explain how method bindings can arise from instances 
of generic method (parameterized method references and raw method references)
- clarified getTypeParameters() to say that these do not show up on the 
binding for instances of the generic method

Olivier, Please reopen if the specs need further changes.