error C2039: '__ctor' : is not a member of 'UpdateMode'

Using VC++ 6.0, if I comment out the StrToUpdateMode() function it compiles fine, but otherwise I get:

error C2039: '__ctor' : is not a member of 'UpdateMode'

I have no idea what it's talking about?

Code:

namespace UpdateMode
{
	enum UpdateMode
	{
		AddOnly		= 0,	/**< Only add record if it doesn't already exist. */
		UpdateOnly	= 1,	/**< Only update record if it exists (i.e. don't add). */
		AddOrUpdate	= 2,	/**< Update record if it exists, otherwise add a new record. */
		Delete		= 3	/**< Delete the record. */
	};

	bool StrToUpdateMode( const TCHAR*  str, UpdateMode::UpdateMode&  updateMode );  // error C2039
}

Nevermind, I removed the UpdateMode:: before the UpdateMode parameter and it works. Comeau doesn't have a problem with the original code. VC++ 6.0 bug?

More likely VC 6.0 more stringently applies the standard.

Comeau doesn't have a problem with the original code. VC++ 6.0 bug?

The MinGW port of g++ 3.4.5 does not report any errors or warnings. However, MSVC8 reports that 'UpdateMode::UpdateMode': must be a class or namespace when followed by '::' on line 11.

I do not know who is correct, but then I usually do not use the same name for an enum as for a namespace.

Since it's inside the namespace, it's not required to explicitly specify the namespace's name within the declaration.

Since it's inside the namespace, it's not required to explicitly specify the namespace's name within the declaration.

That's correct, but fully qualifying the name should also be correct, unless the lookup rules state that in that context UpdateMode refers to the enum, so UpdateMode::UpdateMode refers to a member of the UpdateMode enum.

It would refer to the enum.

You could try ::UpdateMode::UpdateMode instead.

But really, it's just not good style to give a namespace and a contained element the same name.

It would refer to the enum.

Can you quote the C++ Standard on that? It appears that both Comeau and g++ do not conform, yet MSVC6 does, which is amazing.

Too lazy to look it up, but it seems logical. Of course, the issue wouldn't occur for me, because I make sure my names differ.

Too lazy to look it up, but it seems logical.

But the Standard was designed by a committee, and committees can be very illogical at times
Okay, but so can individuals. Oh well.

Of course, the issue wouldn't occur for me, because I make sure my names differ.

Indeed. I think this is the simplest and best solution to the problem.

Yeah, I changed the namespace to UpdateModeNS and it didn't complain about using UpdateModeNS::UpdateMode.
Strange though, you'd think compilers would be smart enough to know what I'm talking about on each side of the ::

Why would you think that compilers are smart?