Search

C4430 emitted twice for the same construct by Dmitry Me

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 697086
Opened: 10/27/2011 8:21:18 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
0
User(s) can reproduce this bug
This behavior is observed in cl.exe 16.00.40219.1

I have this code (taken from http://msdn.microsoft.com/en-us/library/ms173696.aspx):

struct CMyClass {
CUndeclared m_myClass; // line 48
};

which I compile with /W4 and get this output:

1><path>\test.cpp(48): error C2146: syntax error : missing ';' before identifier 'm_myClass'
1><path>\test.cpp(48): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1><path>\test.cpp(48): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int

Here C4430 is emitted twice for the same construct.


Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling version

Visual Studio 2010 SP1

Steps to reproduce

Compile the code above, inspect compiler output.

Product Language

English

Operating System

Windows XP

Operating System Language

English

Actual results

C4430 emitted twice for the same construct.

Expected results

C4430 should be emitted only once for each construct.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 11/1/2011 at 1:17 PM
Hi:
    A fix for this issue has been checked into the compiler sources. The fix should show up in the next release of Visual C++.

Xiang Fan
Visual C++ Team
Posted by MS-Moderator09 [Feedback Moderator] on 10/27/2011 at 7:10 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 10/27/2011 at 8:48 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.