The cost of forsaking C

Re:The cost of forsaking C by creshal on Wednesday October 05, 2016 @06:43AM (#12642815)

On the downside, when it does get updated, compilers take ages to implement the new features, and in the meantime make up busywork like "let's break OS kernels or crypto code to get faster in some random benchmark nobody cares about!"

[ Parent | on HN ]

Re:The cost of forsaking C by dom0 on Wednesday October 05, 2016 @07:58AM (#12643078)

Don't need C updates for that, a GCC upgrade is quite sufficient! :(

[ Parent | on HN ]

Re:The cost of forsaking C by joosters on Wednesday October 05, 2016 @08:49AM (#12643329)

gcc is generally used as a testing ground for new C/C++ features. So in most cases, the compiler supports new features before they are 'officially released' into the language.

It's the complete opposite of waiting for a feature to appear in the compiler.

[ Parent | on HN ]

Re:The cost of forsaking C by creshal on Wednesday October 05, 2016 @09:42AM (#12643683)

GCC didn't get sort-of-complete C11 features until 4.9 (2014) and still omits (largely useless) optional features.

[ Parent | on HN ]