Hacker News new | past | comments | ask | show | jobs | submit login

GCC and clang are probably the only C compilers in the world that care about C11, so it is quite hard to kill C99 for C11.



Last I checked MSVC couldn't even do C99 properly yet.


Because it is called Visual C++ and Microsoft has openly stated that they are compliant to the extent required by ISO C++, which is the future of systems programming on Windows, alongside .NET Native for some use cases.

ISO C++14 requires C99 library compatibility, ISO C++17 requires C11 library compatibility only when C++ doesn't already offer better alternatives.

For C developers there is clang/gcc integration in Visual Studio.

"Modern C++ Game Development on Microsoft Platforms"

https://www.youtube.com/watch?v=on8HMZdAXaw


True, but following the Python model, GCC and Clang could just threaten people with the death of C99 for 5 years or so, then in some release just disable them.

Of course, that would be much less painful than Python 3, because C11 is (a) almost entirely compatible with C99, and (b) not noticeably slower.


AFAIK python 3.5 and 3.6 are significantly faster than 2.7 and uses less memory due to dictionary optimizations. I don’t think speed has been a real argument in a while. Also, python 3 is almost entirely compatible with python 2 (although C is probably even more so).


Everyone would have migrated to python 3 years ago if it was almost entirely compatible with python 2. It's just not.


C and Python's compatibility aren't comparable.

It's quite hard to write a C89 program that isn't C99. Basically any Python 2 program that uses 'print' won't be valid Python 3. Even after fixing that, I always find a bunch of string related problems.


I was given to understand that Python 3 got past after 3.5 or so?


Not only did it get faster as a drop in replacement (assuming you thought ahead at all sometime in the last 10 years), but if you can make use of the new async keywords you can get much faster code after a slight refactor.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: