Bug 102720 - org.eclipse.jdt.core.Signature spec incomplete
Summary: org.eclipse.jdt.core.Signature spec incomplete
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-05 06:00 EDT by Martin Aeschlimann CLA
Modified: 2006-08-07 05:16 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 Martin Aeschlimann CLA 2005-07-05 06:00:47 EDT 
3.1

Signature.getTypeParameter takes a type signature. From the code it seems that 
the first character must be a '<'. Looking at the specs, it wouldn't be possible
that a type signature would start like that.

The spec mentions a FormalTypeParameterSignature. But it doesn't explain the
connection to a type signature.
Comment 1 Philipe Mulet CLA 2005-07-05 07:14:55 EDT 
Type parameter signatures are delimited with '<' and '>',
e.g.  
public abstract class X<E extends Number> implements Runnable {}

would yield the following signature for the type declaration:
<E:Ljava/lang/Number;>Ljava/lang/Object;Ljava/lang/Runnable;
Comment 2 Philipe Mulet CLA 2005-07-05 07:15:09 EDT 
closing
Comment 3 Martin Aeschlimann CLA 2005-07-05 08:06:12 EDT 
My point was that this is not specified in the Javadoc of 'Signature'.
Comment 4 Philipe Mulet CLA 2005-07-05 08:43:51 EDT 
I see. Jerome pls clarify the spec.
Comment 5 Jerome Lanneluc CLA 2006-06-22 06:37:00 EDT 
Added OptionalTypeParameters for type and method signatures in the spec.
Released for 3.3M1 in HEAD.
Comment 6 Frederic Fusier CLA 2006-08-07 05:16:41 EDT 
Verified for 3.3 M1 using build I20060807-0010