Home Dashboard Directory Help

there is no new line at the end of file <initializer_list> in VS2012 Nov 2012 CTP by imoldman



Sign in
to vote
Type: Bug
ID: 773888
Opened: 12/9/2012 7:15:28 AM
Access Restriction: Public
User(s) can reproduce this bug


the code snippet make compile (with /Za option -disable lanuage extensions) complain :

>c:\program files (x86)\microsoft visual c++ compiler nov 2012 ctp\include\initializer_list(64): fatal error C1004: unexpected end-of-file found


#include <initializer_list>

int main() {
    return 0;

Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:22 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 12/17/2012 at 5:18 PM

Thanks for reporting this bug. We've fixed it, and the fix will be available in the next release of our C++ Standard Library implementation. (If you look at the CTP's <initializer_list>, you'll see that it differs dramatically in style from the rest of our STL headers. That's because the compiler team added a temporary "fake" version. We've now picked up the "real" version from Dinkumware, and I verified that we've got a newline at the end now.)

Note: Connect doesn't notify me about comments. If you have any further questions, please E-mail me.

Stephan T. Lavavej
Senior Developer - Visual C++ Libraries
Posted by imoldman on 12/13/2012 at 7:17 PM
@UnitUniverse no pph, you can create a test.cpp and include <initializer_list>, compile, it will be ok; but if you disable lanuage extensions(/Za option in cl), you will see this issue
Posted by UnitUniverse on 12/10/2012 at 12:04 PM
I think it is not a bug. It's the problem about the pre-compiled header configuration. Maybe you can just include 'stdafx.h' header file or just disable the precompiled header on your project-properties.
Posted by Microsoft on 12/10/2012 at 1:35 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 12/9/2012 at 7:52 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.
File Name Submitted By Submitted On File Size  
UploadSummary-121209151508.xml (restricted) 12/9/2012 -
VsInfo.xml (restricted) 12/9/2012 -
DxDiagOutput.txt (restricted) 12/9/2012 -
SolutionFingerprint.6784.html (restricted) 12/9/2012 -