Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330343 - [Xtend] Xtend editor's codecompletion proposesnon present methods
Summary: [Xtend] Xtend editor's codecompletion proposesnon present methods
Status: CLOSED WONTFIX
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-16 07:40 EST by Ulf Rueegg CLA
Modified: 2020-04-30 13:54 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulf Rueegg CLA 2010-11-16 07:40:40 EST
Build Identifier: 20100917-0705

Having two Xtend files with one extending the other. As soon as the extending statement is commented, code completion is still showing the other files methods.

Consider 
foo.ext with method Void foo(): something; 

and bar.ext

extension foo;
Void bar(): 
  foo();

This is correct. But still with following setup codecompletion supposes foo()

//extension foo;
Void bar(): 
  foo();

As soon as the "//extension foo;" line is removed completely the codecompletion works correct again.


Reproducible: Always

Steps to Reproduce:
1. create two .ext files with one exporting the other
2. comment out the extension and try code completion
3. remove the extension and try code completion
Comment 1 Karsten Thoms CLA 2020-04-30 13:54:59 EDT
This is a batch close of open M2T Xpand bugs. It is not planned work on this component in the foreseeable future. If you think this issue needs to be solved and you plan to contribute a fix then feel free to reopen it.