Home Dashboard Directory Help
Search

You got it wrong, again... by Knowing me knowing you, a-ha


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
1
Sign in
to vote
Type: Bug
ID: 667768
Opened: 5/10/2011 11:15:14 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

This should compile:
#include <initializer_list>


int main()
{
    int** p{};
    return 0;
}
Details
Sign in to post a comment.
Posted by ecyrbe on 9/21/2011 at 8:17 AM
Please, add support for this.
VS is lacking c+0x11 support. clang and gcc are almost compliant. You are lagging behind, this is not acceptable.
Posted by Microsoft on 8/10/2011 at 10:25 AM
Hi: yes according the specification of list-initialization (8.5.4) in the draft C++-0x Standard this is a bug. But, unfortunately, as we have not yet had the time to implement this feature so we will not be able to address this "bug" for the next release of Visual C++. But I have noted your interest in this feature and we will consider it for a future release of Visual C++.

Thank you
Jonathan Caves
Posted by Knowing me knowing you, a-ha on 5/20/2011 at 1:02 AM
And if compiler parses it as local function definition then the compiler is buggy in this aspect.
By the way don't you think that local function definition would look rather like this:
int** p(){};
and not like this:
int** p{};

Looking forward to your reply.
Posted by Knowing me knowing you, a-ha on 5/20/2011 at 12:01 AM
N3290 8.5.4 List-initialization [dcl.init.list],page 214. It should compile. Because standard says so.
Posted by Microsoft on 5/19/2011 at 4:02 PM
Hello,

Thank you for your comment. Why do you think it should compile? Compiler parses it as local function definition, which is not supported.

Thanks,
Ulzii Luvsanbat
Windows C++ Team
Posted by Microsoft on 5/15/2011 at 7:45 PM
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 5/13/2011 at 11:14 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.