Bug 138401 - [assist] duplicate proposals for camel case local variables
Summary: [assist] duplicate proposals for camel case local variables
Status: VERIFIED DUPLICATE of bug 132139
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: 3.4 M1   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-25 11:26 EDT by Tom Hofmann CLA
Modified: 2007-08-03 06:56 EDT (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 Tom Hofmann CLA 2006-04-25 11:26:13 EDT 
N20060425

- have the CU below and invoke assist at the caret location (|)

> expected: one proposal proposing "twoPart"
< actual: two identical proposals "twoPart"

------- TwoPart.java ------
class TwoPart {}

class Bug {
    TwoPart two|
}
---------------------------
Comment 1 Frederic Fusier CLA 2006-04-25 12:07:06 EDT 
I do not see any camel case here...!? Did I miss something?
Comment 2 Tom Hofmann CLA 2006-04-25 12:14:46 EDT 
(In reply to comment #1)
> I do not see any camel case here...!? Did I miss something?

TwoPart is a camel case name, and the proposal is based on camel case name generation. My guess is that the duplicate proposal occurs because the name generator tries to approaches which render the same result in this case:

a) existing prefix + postfix from the type's last camel case segment
b) both of the type's segments
Comment 3 David Audel CLA 2006-04-26 04:29:01 EDT 

*** This bug has been marked as a duplicate of 132139 ***
Comment 4 Frederic Fusier CLA 2007-08-03 06:56:55 EDT 
Verified for 3.4M1 using build I20070802-0800.