Bug 204551 - [content assist] Parameter guesser suggests wrong undefined local variable
Summary: [content assist] Parameter guesser suggests wrong undefined local variable
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.6 M1   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 202470
Blocks:
  Show dependency tree
 
Reported: 2007-09-25 10:32 EDT by Dani Megert CLA
Modified: 2009-08-05 02:42 EDT (History)
3 users (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 Dani Megert CLA 2007-09-25 10:32:51 EDT 
R3.3 and 3.4 M2.

Due to the fact that we need a second code assist to get what's in scope and due to the new 3.3 feature of providing proposals for unresolved stuff we now get one wrong argument proposed:
  foo<code assist>
will now also consider local variable foo as possible argument.
Comment 1 Dani Megert CLA 2007-09-25 11:33:31 EDT 
According to David there's nothing JDT Text can do to detect this. Better than providing API to do so would be to fix bug 202470 as in this case we wouldn't need to call code assist for computing the scope.
Comment 2 Olivier Thomann CLA 2009-06-26 10:35:31 EDT 
David, please evaluate.
Comment 3 David Audel CLA 2009-06-29 05:08:48 EDT 
This bug can not occur since JDTText use CompletinContext#getVisibleElements().

Closed as WORKSFORME.
Comment 4 Ayushman Jain CLA 2009-08-05 02:38:59 EDT 
Verified for 3.6M1 using build I20090802-2000