Bug 92569 - Confusing API naming of Signature: getSignatureSimpleName
Summary: Confusing API naming of Signature: getSignatureSimpleName
Status: RESOLVED WONTFIX
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   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-25 08:43 EDT by Martin Aeschlimann CLA
Modified: 2009-08-30 02:35 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-04-25 08:43:52 EDT 
20050425

For inner types like 'a.b.Outer.Inner' getSignatureSimpleName returns 'Outer.Inner'.

To be consistent with other naming, a simple name should only be 'Inner'.
'Outer.Inner' would be called 'type qualifier name' (e.g. as in
IType.getTypeQualifiedName)

As this API is 3.1 it might be worth it to deprecate the current version and
replace it by API 'getTypeQualifierName'.
Comment 1 Jerome Lanneluc CLA 2006-03-28 11:39:50 EST 
Are you saying that Signature#getSignatureSimpleName("La.b.Outer.Inner;") returns "Outer.Inner" ?
Comment 2 Martin Aeschlimann CLA 2006-03-28 12:03:50 EST 
Yes, the spec says:
 getSignatureSimpleName("Ljava.util.Map$Entry") -> "Map.Entry"

As mentioned, this API uses the terms 'SimpleName' in a misleading (unconsistent) way. You can't really call 'Map.Entry' a simple name, can you?

I suggest to reopen: Deprecated the method and give it the correct name. 'getTypeQualifiedName'
Comment 3 Jerome Lanneluc CLA 2006-03-29 06:51:10 EST 
reopening
Comment 4 Jerome Lanneluc CLA 2006-03-29 06:51:32 EST 
Post 3.2
Comment 5 Eclipse Webmaster CLA 2009-08-30 02:35:31 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.