spongo2

Hi! I'm Steve the C++ dev manager in Visual Studio. No, VS for Mac does not currently have C++ support but thanks for the feedback.

One thing you could do is register your opinion here: https://visualstudio.uservoice.com/forums/563332-visual-stud...

see replies elsewhere. We demo'd C99 support via Clang / C2 on stage at CppCon.

we made a bunch of improvements to build throughput especially for incremental builds. many improvements to our handling of template code as well. -- steve, vc dev mgr

we are targeting C99 via the new Clang / C2 hybrid compiler. We demoed it on stage at CppCon this week.

correct.

Hi Chandler! it's probably worth mentioning that we will be also opening up our lldb-mi based debug engine which will allow you to debug any lldb target from Visual Studio. And we'll continue to contribute back improvements to lldb-mi. Thanks, Steve Carroll, VC Dev Mgr

see Jim Radigan's build talk on compiling Objective-C for windows for more info on this :)

Hi DannyBee, sorry if we didn't get the message out clearly. Jim Radigan gives a deeper technical explanation in the build talk he did yesterday. http://channel9.msdn.com/events/Build/2015/3-610 It's translating LLVM IR to C2 IR. We know that the Clang/LLVM community is hard at work on implementing the MS-ABI and we've reached out to a few developers working on ABI stuff as well as symbols support. We intend to engage with that community more openly now that we've announced but of course shipping the code will be our top priority. One important contribution of the Clang/C2 approach is that we will have full native VS debugger support. This is just the first step in a longer journey. Thanks, Steve, VC Dev Mgr

We are announcing that we will ship a hybrid compiler that combines the clang frontend with the c2 existing backend. We will fully support that for building portable code within Visual Studio for Windows. We definitely don't want to take credit for the clang community's work. We have a ton of respect for those developers. We intend to make contributions back to the community and we've started to reach out to some of the relevant parties. Thanks, Steve, VC Dev Mgr

yes, we are well aware that clang and llvm is working on targeting windows. this is clang+c2 which we will fully support.

http://clang.llvm.org/docs/MSVCCompatibility.html says minimal. Note that this is about cross-plat conformant c++ code. SEH is windows specific.

correct, this will use MS libraries. If you watch Jim Radigan's Build talk (he owns C2), he talks a little bit about how the ABI is really a part of the platform and it might clarify some of this. http://channel9.msdn.com/Events/Build/2015/3-714 about 23 minutes in. Thanks, Steve (vc dev mgr)

VC++ dev mgr here. I replied to a similar question above. please let check that out.

Hey, VC++ Dev Mgr here. Our official statement hasn't changed which is that we will enable major libraries but we need to prioritize C++ over C. Let me know if there is a library that is blocked that we don't know about and I will see what we can do. I will also say that the requests for C99/C11 seem to be increasing and we are listening. :)

Our current statement of support is that we support enough of C99 to unblock commonly used libraries. We support a large swath of C99 but it is correct that our support isn't complete yet as we prioritized C++ conformance. If there is a C99 library that you need to use that we don't work with, please let me know. (I'm the VC++ dev manager)