3 ms·

FYI, C99 printf including 'z' for size_t was fully implemented in VS 2015.

• pjmlp 11y ago
  Most likely you are not allowed to comment on it, but has the official position from the last C9 VS team interviews changed?
  • StephanTLavavej 11y ago
    I believe we're hoping that Clang/C2 will satisfy those who want to build C99 TUs on Windows. Personally, I have absolutely no interest in C99 (I wasted a year and a half of my life learning C before C++).
    • spongo2 11y ago
      correct.
    • pjmlp 11y ago
      Thanks for replying. I had a similar experience back in the MS-DOS days still, and share the same opinion. Turbo Pascal -> C (meh) -> C++ (great back in business!) Even though I mostly do JVM and .NET nowadays, still enjoy playing with C++ on the side, specially for mobile OS coding. I see dropping C support on Windows as a means to force developers to migrate to more secure languages, but of course Microsoft should do what makes business sense.
• to3m 11y ago
  Thanks for the note. Switching to VS2015 just worked its way up my to do list.
  • StephanTLavavej 11y ago
    You'll want to read these changelogs for the CRT and the STL: http://blogs.msdn.com/b/vcblog/archive/2014/06/18/crt-features-fixes-and-breaking-changes-in-visual-studio-14-ctp1.aspx http://blogs.msdn.com/b/vcblog/archive/2014/06/18/crt-featur... , http://blogs.msdn.com/b/vcblog/archive/2014/06/06/c-14-stl-features-fixes-and-breaking-changes-in-visual-studio-14-ctp1.aspx http://blogs.msdn.com/b/vcblog/archive/2014/06/06/c-14-stl-f... , and http://blogs.msdn.com/b/vcblog/archive/2015/07/14/stl-fixes-in-vs-2015-part-2.aspx http://blogs.msdn.com/b/vcblog/archive/2015/07/14/stl-fixes-... .