BUG: Wrong Namespace Member Selected for Qualified ID

Last reviewed: May 21, 1997
Article ID: Q167321
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

The wrong member function is called if you:

  • define a class with the same name, in different scopes;
  • create a temporary object, as shown in the sample, of that class type;
  • call a member function of that class.

Look at the More Information section for a sample that demonstrates the problem and the workaround.

RESOLUTION

Do not create a temporary object. Instead create a local object, and then call the member functions through the local object.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following sample demonstrates the problem and the workaround.

SAMPLE

   /*
   Compile Options: /GX
   */
   # include <iostream>
   using namespace std ;

   struct CMyClass
   {
      virtual void DoSomething()
      {
         cout << "::CMyClass::DoSomething()\n";
      }
   };

   namespace MyNameSpace
   {
      struct CMyClass
      {
         virtual void DoSomething()
         {
            cout << "MyNameSpace::CMyClass::DoSomething()\n";
         }
      };
   }

   int main()
   {
      MyNameSpace::CMyClass().DoSomething() ;
      // Workaround: Comment the line above,
      // Uncomment the following lines
      // MyNameSpace::CMyClass C1 ;
      // C1.DoSomething();
      return 0;
   }


Additional query words: namespace
Keywords : CPPIss CPPLngIss kbcode vcbuglist500 kbbuglist
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.