4 ms·
>> read the standard >> Casey Muratori, who's a better C programmer than me, is of the opinion that you should check your compiler's behavior rather than read
by dottrap 10y ago
>> read the standard
>> Casey Muratori, who's a better C programmer than me, is of the opinion that you should check your compiler's behavior rather than read standards.
In Casey Muratori's case, he's the type of person who cares to understand what the compiler is actually generating under the hood. He doesn't exactly trust the compiler to always do the right thing.
There was an episode of Handmade Hero where he caught an optimization #fail of the compiler and tried to figure out what was going on (live).
https://twitter.com/cmuratori/status/596775025023287297 https://twitter.com/cmuratori/status/596775025023287297
Casey Muratori also has been developing in Visual Studio for a very long time. Visual Studio has a long, tortuous, history of being non-stanards compliant and buggy. And Microsoft until very recently, never cared to fix anything. (And it still doesn't conform to C99, let alone C11.)
- slededit 10y agoThe Visual C compiler is only for backwards compatibility. If you are looking for improved C compilation you'll be waiting a very long time. The only improvements they've made were those also required for C++.
- pjmlp 10y agoMicrosoft already stated multiple times that the focus of Visual C++ is C++ (hence the name). Whatever C related updates you might see, are the ones required by the ANSI C++ for C compatibility. For C99 and C11 support there is the clang frontend to C2, the Visual C++ backend, currently taking an LLVM role at Microsoft, being shared between clang, VC++ and .NET Native.