Search

Decades old, missing "C99" headers ever coming to VS' stack? by Real McCoy

Active

8
0
Sign in
to vote
Type: Bug
ID: 773523
Opened: 12/5/2012 3:19:26 AM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug
Please implement and make available the <stdbool.h> and other missing headers like <inttypes.h> etc. from C99 and C++'s <cinttypes.h> (reported on Connect: http://connect.microsoft.com/VisualStudio/feedback/details/748766/) to VS2012's headers pool. It will help us porting open-source projects from other platforms to Windows ecosystem with ease. For an instance, the Giflib project (http://sourceforge.net/projects/giflib/) requires stdbool.h


Please show some love to C99 and C11 in your ongoing efforts.
Details (expand)

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

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce

Create any C/C++ project in VS2012. Include C's stdbool.h, inttypes.h and C++'s cinttypes.h

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Those and some other standard headers from C99, C11 and C++ are not available in Visual C world. As an alternative -- yet costly -- solution, the developers have to go an extra mile to mimic the implementation for Windows environment.

Expected results

We need all C99, C11 and C++ standards libraries in VS2012. So porting projects from other platforms is easy.

We need Microsoft to show some love to C99 and C11.

Locale

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 12/5/2012 at 6:45 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Upon review of this issue , we have identified it as a duplicate Connect bug. We have closed this bug as a duplicate, and added a vote to the original bug http://connect.microsoft.com/VisualStudio/feedback/details/748766/. Please check the original feedback item for any updates and any resolutions.
Posted by Microsoft on 12/5/2012 at 3:50 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.