Visual Studio support for new C / C++ standards?

by

MS has a series of public replies to this, most of them blaming their users. Like this one:

https://devblogs.microsoft.com/cppblog/iso-c-standard-update/

Now, the Visual C++ compiler team receives the occasionally question as to why we haven’t implemented C99. It’s really based on interest from our users. Where we’ve received many requests for certain C99 features, we’ve tried to implement them (or analogues). A couple examples are variadic macros, long long, __pragma, __FUNCTION__, and __restrict. If there are other C99 features that you’d find useful in your work, let us know! We don’t hear much from our C users, so speak up and make yourselves heard

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=345360

Hi: unfortunately the overwhelming feadback we get from the majority of our users is that they would prefer that we focus on C++-0x instead of on C-99. We have “cherry-picked” certain popular C-99 features (variadic macros, long long) but beyond this we are unlikely to do much more in the C-99 space (at least in the short-term).

Jonathan Caves

Visual C++ Compiler Team.

This is a pretty sad state of affairs, but also makes sense if you suspect MS wants to lock users in: it makes it very hard to port modern gcc-based code into MSVC, which at least I find extremely painful.

A workaround exists, though: Note that Intel is much more enlightened on this. the Intel C compiler can handle C99 code and even has the same flags as gcc, making it much easier to port code between platforms. Also, the Intel compiler works in visual studio. So by scrapping MS COMPILER you can still use the MS IDE that you seem to think has some kind of value, and use C99 to your hearts content.

A more sensible approach is honestly to move over to Intel CC or gcc, and use Eclipse for your programming environment. Portability of code across Windows-Linux-Solaris-AIX-etc is usually important in my experience, and that is not at all supported by MS tools, unfortunately.

More Related Contents:

  1. Visual Studio 2012 __cplusplus and C++ 11
  2. Is there any option to switch between C99 and C11 C standards in Visual Studio?
  3. error LNK2019: unresolved external symbol _WinMain@16 referenced in function ___tmainCRTStartup
  4. Unresolved external symbol in object files
  5. What is “Expression SFINAE”?
  6. Can’t pass temporary object as reference
  7. C++11 features in Visual Studio 2012
  8. Automatically stop Visual C++ 2008 build at first compile error?
  9. C++11 inheriting constructors and access modifiers
  10. std::to_string – more than instance of overloaded function matches the argument list
  11. Initializer list not working with vector in Visual Studio 2012? [duplicate]
  12. Assertion failed (size.width>0 && size.height>0)
  13. “newly” installed visual studio returns 408 errors on blank program of type ‘cannot open source file “errno.h” ‘
  14. Visual Studio 2010’s strange “warning LNK4042”
  15. Errors when linking to protobuf 3 on MS Visual C
  16. Variadic Template in VS 2012 (Visual C++ November 2012 CTP)
  17. Double delete in initializer_list vs 2013
  18. trying to use VideoCapture and imshow(), raises Assertion failed (size.width>0 && size.height>0) in cv::imshow
  19. Fatal error: “No Target Architecture” in Visual Studio
  20. VC++ fatal error LNK1168: cannot open filename.exe for writing
  21. Problems with running EXE file built with Visual Studio on another computer
  22. How to load a custom binary resource in a VC++ static library as part of a dll?
  23. Disabling Warnings generated via _CRT_SECURE_NO_DEPRECATE
  24. Expand macro inside string literal
  25. std::thread::join() hangs if called after main() exits when using VS2012 RC
  26. how to specify vc11 lambda calling convention
  27. Visual Studio 2008 with c++11
  28. Workaround for error C2536: cannot specify explicit initializer for arrays in Visual Studio 2013
  29. Explicit Return Type of Lambda
  30. Why can’t Visual Studio find my DLL? [duplicate]

Leave a Comment