template <typename InnerType> class PtrTest
{
public:
	InnerType* ptr;
	InnerType* operator->()	{return ptr;}
};

struct Test1
{
	int someVar;
};

namespace TestNameSpace
{
	struct Test2
	{
		int someOtherVar;
	};
}

int main()
{
	PtrTest<Test1> test1;
	test1->|;	// correctly suggests 'someVar'

	PtrTest<::Test1> test1_2;
	test1_2->|;	// doesn't suggest anything

	PtrTest<::TestNameSpace::Test2> test2;
	test2->|;	// doesn't suggest anything

	using ::TestNameSpace::Test2;
	PtrTest<Test2> test2_2;
	test2_2->|;	// correctly suggests 'someOtherVar'

	typedef ::TestNameSpace::Test2 Test2_3;
	PtrTest<Test2_3> test2_3;
	test2_3->|;	// doesn't suggest anything

	typedef Test1 Test1_3;
	PtrTest<Test1_3> test1_3;
	test1_3->|;	// doesn't suggest anything
}

quote:

---

Originally posted by o2a

(Btw, history for build 1525 states that "case 4801" in context of std::string is fixed and links to my previously reported std::auto_ptr problem; but that one doesn't seem to be fixed yet. Just for the record. ;)

---

quote:

---

Originally posted by feline
right, before i go raising any cases, lets see if we are seeing the same things.

i am using VS2003 and VA 1525, with content from default intellisense turned off.

---

quote:

---

test1 = typing -> produces a completion listbox automatically, with just the item "someVar"

---

quote:

---

test1_2 = typing -> does not produce anything, but pressing CTRL-SPACE produces a completion listbox with just the item "someVar". if i accept this suggestion then "someVar" is underlined as a mistyped symbol.

---

quote:

---

test2 = typing -> does not produce anything, and pressing CTRL-SPACE simply makes the IDE beep, no completion listbox.

type someOtherVar and it is underlined as a mistyped symbol.

---

quote:

---

test2_2 = typing -> produces a completion listbox automatically, with just the item "someOtherVar"

---

quote:

---

test2_3 = typing -> does not produce anything, but pressing CTRL-SPACE produces a completion listbox with just the item "someOtherVar". if i accept this suggestion then everything is fine, no underlining at all.

---

quote:

---

test1_3 = typing -> does not produce anything, but pressing CTRL-SPACE produces a completion listbox with just the item "someVar". if i accept this suggestion then everything is fine, no underlining at all.

---

quote:

---

Originally posted by support

Thanks for the detailed example. All of the above cases should be fixed in 1526.

---

template <typename InnerType> class PtrTest
{
public:
	InnerType* ptr;
	InnerType* operator->()	{return ptr;}
};


/////////////////////////////////////////////////////////////////////////////////////////
// code in one namespace using class from another namespace, both in global scope
namespace TestSpace
{
	struct Test2
	{
		int someOtherVar;
	};
}

namespace OtherSpace1
{
	void test()
	{
		// 'Test2' insufficiently qualified
		// - should be 'TestSpace::Test2' actually, but VAX still recognizes it
		PtrTest<Test2> test1;
		test1->|;	// works (incorrectly actually)
		// (suggests 'someOtherVar')

		// 'TestSpace::Test2' correctly qualified
		PtrTest<TestSpace::Test2> test2;
		test2->|;	// works (suggests 'someOtherVar')
	}
}


//////////////////////////////////////////////////////
// same as above, but now the class is in a namespace 
// being a child of the code's namespace
namespace OuterSpace
{
	////////////////////////////////////////////////
	namespace InnerSpace1
	{
		struct Test2
		{
			int innerVar;
		};
	}

	////////////////////////////////////////////////
	void testOuter()
	{
		// 'Test2' insufficiently qualified
		// but VAX recognizes ONE of the 'Test2'-classes here
		PtrTest<Test2> test1;
		test1->|;	// VAX assumes '::TestSpace::Test2'
		// (suggests 'someOtherVar')

		// '::TestSpace::Test2' correctly qualified
		// (without explicit global scope qualifier)
		PtrTest<TestSpace::Test2> test2;
		test2->|;	// works (suggests 'someOtherVar')

		// '::TestSpace::Test2' correctly qualified 
		// (with explicit global scope qualifier)
		PtrTest<::TestSpace::Test2> test3;
		test3->|;	// works (suggests 'someOtherVar')

		// 'InnerSpace1::Test2' locally qualified
		PtrTest<InnerSpace1::Test2> test4;
		test4->|;	// DOESN'T WORK 
		// (old behaviour -> no suggestion list box at all)

		// 'InnerSpace1::Test2' globally qualified
		PtrTest<::OuterSpace::InnerSpace1::Test2> test5;
		test5->|;	// NEARLY works ;)
		// (correctly suggests 'innerVar' 
		//  AND incorrectly 'someOtherVar' too)
	}

	////////////////////////////////////////////////
	// here same situation as first case 
	// (both namespaces at same level) but inside a common namespace
	namespace InnerSpace2
	{
		void testInner()
		{
			// 'InnerSpace1::Test2' locally qualified
			PtrTest<InnerSpace1::Test2> test4;
			test4->|;	// DOESN'T WORK 
			// (old behaviour -> no suggestion list box at all)
	
			// 'InnerSpace1::Test2' globally qualified
			PtrTest<::OuterSpace::InnerSpace1::Test2> test5;
			test5->|;	// NEARLY works ;)
			// (correctly suggests 'innerVar' 
			//  AND incorrectly 'someOtherVar' too)
		}
	}
}

////////////////////////////////////////////////
void testGlobal()
{
	// 'InnerSpace1::Test2' globally qualified
	PtrTest<::OuterSpace::InnerSpace1::Test2> test5;
	test5->|;	// NEARLY works ;)
	// (correctly suggests 'innerVar' 
	//  AND incorrectly 'someOtherVar' too)
}

int main()
{
}

		typedef InnerSpace1::Test2* InnerTest2Ptr;
		InnerTest2Ptr test4_1;
		test4_1->|;	// DOESN'T WORK 

		InnerSpace1::Test2* test4_2;
		test4_2->|;	// DOESN'T WORK 

		typedef ::OuterSpace::InnerSpace1::Test2* InnerTest2Ptr_2;
		::OuterSpace::InnerTest2Ptr_2 test4_3;
		test4_3->|;	// works

		::OuterSpace::InnerSpace1::Test2* test4_4;
		test4_4->|;	// works