stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Created: (STDCXX-74) [MSVC 8.0] type_info pollutes the global scope
Date Wed, 30 Nov 2005 01:43:31 GMT
[MSVC 8.0] type_info pollutes the global scope

         Key: STDCXX-74
     Project: STDCXX
        Type: Bug
  Components: External  
    Versions: 4.1.2    
 Environment: MSVC 8.0
    Reporter: Martin Sebor
 Assigned to: Martin Sebor 


Bug Details: type_info pollutes the global scope
Bug ID:         FDBK40150
Problem Type:   Bug
Status:         Closed
Resolution:     Won't Fix
Microsoft Status:       Reviewed
Opened Date:    2005-11-09 12:10:56
Opened By:      Martin Sebor
Product/Technology:     Visual C++
Version:        Visual Studio 2005
Product Language:       English
Category:       Libraries
OS:     Windows 2000 Professional
OS Language:    US English
Submission Language:    English
Opened by Martin Sebor on 2005-11-09 at 12:10:56
The symbol type_info introduced by the C++ standard library into the global scope causes clashes
with user-defined symbol of the same name.

Resolved as Won't Fix by Microsoft on 2005-11-15 at 14:14:13
Thank you for reporting this. When support was added for these templates, there were not a
proper namespace support in the compiler. Changing this right now is not possible because
of backward compatability. We would really like to fix this but unfortunately without other
substantial changes we won't be able to do so.

Nikola Dudar
Visual C++
Steps to Reproduce:
$ cat t.cpp && cl -EHsc -c t.cpp
#include <iostream>

template <class T>
void type_info () { }
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.

t.cpp(4) : error C2904: 'type_info' : name already used for a template in the current scope
C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE\typeinfo(43) : see declaration of 'type_info'
Actual Results:         Compilation errors.
Expected Results:       No errors.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message