[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::visual

Title:Microsoft Visual C++ bug reports and kits
Notice:Register in Topic 2. 5.Last for latest Kit
Moderator:DECWET::THOMASN
Created:Tue May 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:521
Total number of notes:2938

477.0. "VC5.0 Namespace with Template Problems" by OZROCK::MOORE (Stephen Moore) Mon Mar 10 1997 21:04

Hi again,

Following on from my earlier note, the problem I have discovered is demonstrated
by compiling the following code. It seems that templates do not handle namespace
qualifiers very well.

As a test, I've added the line 
	
	using A::X; 

into namespace B, but the compiler still fails. The only solution I have found
that works is to add the line

	using namespace A;

But this solution defeats the whole purpose of using namespaces.

Regards
Steve


//test.cxx
#include <deque>

namespace A
{
	class X {};
}

namespace B
{
	std::deque<A::X> collection;
}


Compiling...
test.cxx

e:\Program Files\DevStudio\Vc\include\deque(229) : error C2065: 'X' : undeclared
identifier

e:\Program Files\DevStudio\Vc\include\deque(229) : error C2440: 'default
argument' : cannot convert from 'int' to 'class A::X'

No constructor could take the source type, or constructor overload resolution
was ambiguous

Error executing cl.exe.

test.obj - 2 error(s), 0 warning(s)
T.RTitleUserPersonal
Name		DateLines
477.1DECWET::THOMASBug-for-bug compatible with IntelTue Mar 11 1997 08:337
    Stephen,
    
    It's going to be a while before any of us can reboot both an Alpha and
    an Intel back to a 4.2b installation. Can you check whether this is
    also a problem on Intel?
    
    Thanks ... Mike
477.2OZROCK::MOOREStephen MooreTue Mar 11 1997 15:3420
Mike,

Unfortunately I don't have an intel V5 kit yet, however I strongly suspect it is
a problem on this intel also as indicated by a reply to my previous note and
a feeling I have gained from reading microsoft.public.vc.language.


> It's going to be a while before any of us can reboot both an Alpha and
>  an Intel back to a 4.2b installation.

don't understand what you mean here, are you attempting to find out if the
problem exists on 4.2b as well. My impression of V4 and namespaces is that it
was broken fairly major, so I'd be very surprised if the problem doesn't exist
on V4.

As soon as a get an intel V5 kit (should be within a week) I'll let you know 
the result.

Cheers
Steve.
477.3DECWET::THOMASBug-for-bug compatible with IntelThu Mar 13 1997 13:3718
>> It's going to be a while before any of us can reboot both an Alpha and
>>  an Intel back to a 4.2b installation.
>
>don't understand what you mean here, are you attempting to find out if the
>problem exists on 4.2b as well. My impression of V4 and namespaces is that it
>was broken fairly major, so I'd be very surprised if the problem doesn't exist
>on V4.
    
    Sorry, I still have 4.2b on the brain, and had forgotten you were
    talking about 5.0.
    
    And of course you can't try it on the Intel kit yet - it hasn't
    released. My apologies for being so confused :-(
    
>As soon as a get an intel V5 kit (should be within a week) I'll let you know 
>the result.
    
    That would be good. Thanks.