Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353966 - [editor] nested names resolved within unresolved namespace
Summary: [editor] nested names resolved within unresolved namespace
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: M7   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-05 02:52 EDT by Ed Willink CLA
Modified: 2013-05-20 11:37 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 Ed Willink CLA 2011-08-05 02:52:54 EDT 
In "A::B::C", if A cannot be resolved A is reported as unresolved, but resolution of B then occurs in the global not A's namespace, so B may be spuriously resolved.

ModelElementCSScopeAdapter.get...Namespace must provide an InvalidNamespace object resolution for A so that it stops being a proxy.
Comment 1 Ed Willink CLA 2012-02-18 06:48:10 EST 
Fixed by introduction of PathNameCS to facilitate Completion Proposals
Comment 2 Ed Willink CLA 2012-05-02 15:12:44 EDT 
pushed to master
Comment 3 Ed Willink CLA 2013-05-20 11:37:31 EDT 
CLOSED after a year in the RESOLVED state.