Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 57692 - [Content Assist] CompletionEngine::completionOnSingleNameReference() behaviour incorrect
Summary: [Content Assist] CompletionEngine::completionOnSingleNameReference() behaviou...
Status: VERIFIED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Hoda Amer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 51841
Blocks: 50152
  Show dependency tree
 
Reported: 2004-04-07 00:47 EDT by John Camelon CLA
Modified: 2009-01-09 17:00 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Camelon CLA 2004-04-07 00:47:20 EDT
Now that we got rid of SCOPED_REFERENCE as a CompletionKind, 
SINGLE_NAME_REFERENCE is used in significantly more places.  Although I have 
updated the parser to do the proper thing for scoped references, I am unable 
to get CompletionFailedTest_ScopedReference_NoPrefix_Bug50152 to pass, as 
within the Method, we lookup THIS & LOCAL_VARIABLES and not nested classes 
within namespaces.  

Likewise, ASTNode.lookup() assumes that the context provided is a class when 
that is now not true ... 
   if( !thisContainer.isVisible( s, qualification ) ) 

I had to hack ParserSymbolTable.getVisibility() to not throw an Error() when 
it tried to check a method's visibility to a namespace (exclusively an 
IContainerSymbol).
Comment 1 John Camelon CLA 2004-04-07 00:49:42 EDT
Add dependency upon https://bugs.eclipse.org/bugs/show_bug.cgi?id=51841 as 
they are related (we need to get more specific contexts in the completion node 
and we need to have both Lookup() and CompletionEngine asking very precise 
questions.  
Comment 2 Hoda Amer CLA 2004-04-12 17:18:25 EDT
Fixed in HEAD.
Comment 3 James Ciesielski CLA 2004-04-20 10:16:59 EDT
John/Hoda, can you please verify this bug as fixed and mark it as such?