Bug 61860 - Code completion: potential method decl completion on return type
Summary: Code completion: potential method decl completion on return type
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-12 04:28 EDT by Martin Aeschlimann CLA
Modified: 2004-05-12 14:47 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 2004-05-12 04:28:58 EDT 
20040512

I currently get a call to acceptPotentialMethodDeclaration on return types of
existing methods

public Vector foo() {}
          ^code assist here

what leads me to suggest to create 'Vec'.

this seems like a bug. there are also no overridden method suggested at such
locations.
Comment 1 David Audel CLA 2004-05-12 09:49:07 EDT 
I cannot reproduce the problem with your test case.
I can with the following test case
public class X {
  Vect<cursor>or foo() {}
}

In this case the proposals are
  - overvidden methods which start with "Vec"
  - a call to acceptPotentialMethodDeclaration

This behavior is currently considered as correct because CodeAssist does not 
look after cursor location.
Comment 2 Martin Aeschlimann CLA 2004-05-12 14:47:46 EDT 
you're right, it seems to be fixed now.