Linked by R_T_F_M on Thu 13th Sep 2012 21:19 UTC
FreeBSD "For the past several years we've been working towards migrating from GCC to Clang/LLVM as our default compiler. We intend to ship FreeBSD 10.0 with Clang as the default compiler on i386 and amd64 platforms. To this end, we will make WITH_CLANG_IS_CC the default on i386 and amd64 platforms on November 4th."
Thread beginning with comment 534988
To read all comments associated with this story, please click here.
C++
by kwan_e on Fri 14th Sep 2012 01:26 UTC
kwan_e
Member since:
2007-02-18

Ironic, now that the biggest projects written in C are compiled with something written in C++ (or, increasingly so, in GCC's case).

Reply Score: 3

RE: C++
by satsujinka on Fri 14th Sep 2012 03:02 in reply to "C++"
satsujinka Member since:
2010-03-11

There's nothing ironic about it. Different projects use different languages.

Reply Parent Score: 2

v RE[2]: C++
by kwan_e on Fri 14th Sep 2012 06:02 in reply to "RE: C++"
RE: C++
by moondevil on Fri 14th Sep 2012 07:26 in reply to "C++"
moondevil Member since:
2005-07-08

I think people are slowly accepting that C++ eventually gets to replace C in most areas where C is still relevant in the desktop/server.

MacOS X device drivers are done in C++ (IOKit).

Most of the Win32 APIs since Windows 2000 are actually COM based and Microsoft publicly announced that C is only relevant for legacy code and they rather focus in C++. More so in Windows 8.

Symbian and BeOS are done in C++.

Only Linux and BSD are still have pure C/ASM kernels. I don't know about Aix, HP-UX and Solaris.

Now for embedded systems C still have a place, as many of them are still coded in Assembly and companies are now slowly moving up to C.

Of course C will exist for decades still, as it does not make sense to rewrite code that works just for changing language.

Reply Parent Score: 12

RE[2]: C++
by Valhalla on Fri 14th Sep 2012 14:12 in reply to "RE: C++"
Valhalla Member since:
2006-01-24

I think people are slowly accepting that C++ eventually gets to replace C in most areas where C is still relevant in the desktop/server.

I seriously doubt that, not only from my own experience but also from what I've see of the language popularity benchmarks C is holding on as strong as ever (it recently beat Java for the top spot on Tiobe).


MacOS X device drivers are done in C++ (IOKit).

Actually it uses a subset of C++ with no exceptions, no templates, no multiple inheritance etc, which kind of begs the question why they couldn't just settle with plain C to begin with for those drivers.

C is here to stay, it's the lowest common denominator as far as high level languages go, supported by pretty much every platform, and useable from just about any other language.

That doesn't mean it's the best choice for every project, there are certainly areas in which other languages like C++, Java, C#, Python, Go, etc are likely better choices as they offer a higher level of abstraction.

A particular area in which I wager C will always reign supreme is in library/framework code, the reason projects like zlib, flac, libjpeg, png, sdl, audio/video codecs, lzma, etc etc are written in C is because it's A) fast and small memory footprint B) callable from just about anything.

Also none of the 'new' languages really compete with C, new languages like Go, Rust are higher level and compete primarily with C++ or even higher level languages.

Reply Parent Score: 3