Summary: | [DOM] ASTNode APIs should specify types of property descriptors | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | trivial | ||||||
Priority: | P3 | CC: | amj87.iitr | ||||
Version: | 3.7 | ||||||
Target Milestone: | 3.7 M2 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Markus Keller
2010-08-12 18:12:04 EDT
Created attachment 178084 [details]
Proposed fix
Released for 3.7M2. Verification has to be done by code inspection. Looks mostly good, but I disagree with the description of properties with a primitive type. The Javadoc should not use the boxed type. The setters and getters that use property descriptors deal with the boxing/unboxing. E.g. BooleanLiteral#BOOLEAN_VALUE_PROPERTY says "(type: {@link Boolean})", but the SimplePropertyDescriptor is created with "boolean.class" and thus SimplePropertyDescriptor#getValueType() also returns "boolean.class" and not "Boolean.class". Regex to narrow down the places that need adjustments: \b[a-z]+\.class\b So you suggest: (type: {@link boolean.class}) ? > (type: {@link boolean.class})
Unfortunately, Javadoc can't create @link links to primitive types, so it would be (type: <code>boolean</code>).
But thinking about it again, we should probably leave it as you did it. When SimplePropertyDescriptor gets generified, the type argument for boolean properties will also be Boolean and not boolean. Marking as fixed again.
Verified for 3.7M2 using code inspection. |