Home Dashboard Directory Help
Search

VS2012 RC macro _VARIADIC_MAX = 7 is broken by Silicon Kiwi


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 746478
Opened: 6/4/2012 4:10:26 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Defining _VARIADIC_MAX == 7 results in a completely broken builds.

It is caused by a typo error in <xstddef>

Line 453 reads: #define _PAD_LIST2    _PAD_LIST0_6

should be:

#define _PAD_LIST2    _PAD_LIST0_5
Details
Sign in to post a comment.
Posted by Microsoft on 10/9/2012 at 4:32 PM
Hi again,

We've fixed this bug, and the fix will be available in the next update to our C++ Standard Library implementation.

STL
Posted by Microsoft on 6/18/2012 at 2:14 PM
Hi,

Thanks for reporting this bug. I'm Microsoft's maintainer of the STL, and I wanted to let you know that while this bug remains active in our database, it won't be fixed in VC11 RTM (VS 2012 RTM). All bugs are important to us, but some are more severe than others and rise to the top of our priority queue.

I'm copying-and-pasting this response across all of the STL's active Connect bugs, but the following terse comments apply specifically to your bug:

* This is an obvious and simple typo - it was just reported too late for us to fix in RTM (getting any fixes in at this point requires going through a lot of process and validation - this bug has a trivial workaround so it doesn't qualify). We'll either fix the typo or completely rip out this machinery in favor of real variadic templates.

I can't promise when we'll be able to resolve this bug, but we hope to do so as soon as possible (and I'll send another response when that happens) - our first opportunity will be the "out of band" release between VC11 and VC12 that Herb Sutter announced at the GoingNative 2012 conference.

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
stl@microsoft.com
Posted by Microsoft on 6/5/2012 at 3:58 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 MS-Moderator01 on 6/4/2012 at 4:42 PM
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.