Bug 102720

Summary:	org.eclipse.jdt.core.Signature spec incomplete
Product:	[Eclipse Project] JDT	Reporter:	Martin Aeschlimann <martinae>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.1
Target Milestone:	3.3 M1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Martin Aeschlimann

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

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

2005-07-05 07:15:09 EDT

closing

Comment 3 Martin Aeschlimann

2005-07-05 08:06:12 EDT

My point was that this is not specified in the Javadoc of 'Signature'.

Comment 4 Philipe Mulet

2005-07-05 08:43:51 EDT

I see. Jerome pls clarify the spec.

Comment 5 Jerome Lanneluc

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

2006-08-07 05:16:41 EDT

Verified for 3.3 M1 using build I20060807-0010