Re:Rejuvenating the Microsoft C/C++ Compiler
by StephanTLavavej on Friday September 25, 2015 @11:33AM
(#10278704)
FYI, C99 printf including 'z' for size_t was fully implemented in VS 2015.
[ Parent
| on HN ]
Re:Rejuvenating the Microsoft C/C++ Compiler
by pjmlp on Friday September 25, 2015 @12:21PM
(#10279023)
Most likely you are not allowed to comment on it, but has the official position from the last C9 VS team interviews changed?
Re:Rejuvenating the Microsoft C/C++ Compiler
by StephanTLavavej on Friday September 25, 2015 @09:05PM
(#10281672)
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++).
Re:Rejuvenating the Microsoft C/C++ Compiler
by pjmlp on Saturday September 26, 2015 @02:28AM
(#10282322)
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.
Re:Rejuvenating the Microsoft C/C++ Compiler
by spongo2 on Friday September 25, 2015 @10:51PM
(#10281907)
correct.
Re:Rejuvenating the Microsoft C/C++ Compiler
by to3m on Friday September 25, 2015 @07:19PM
(#10281316)
Thanks for the note. Switching to VS2015 just worked its way up my to do list.
Re:Rejuvenating the Microsoft C/C++ Compiler
by StephanTLavavej on Friday September 25, 2015 @09:07PM
(#10281684)
You'll want to read these changelogs for the CRT and the STL: 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-f... , and http://blogs.msdn.com/b/vcblog/archive/2015/07/14/stl-fixes-... .