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."
Permalink for comment 535158
To read all comments associated with this story, please click here.
RE[5]: C++
by moondevil on Sat 15th Sep 2012 06:53 UTC in reply to "RE[4]: C++"
moondevil
Member since:
2005-07-08

Ever tried to link a program unit written in C++ into a project written FORTRAN? It's possible, but ugly. It's much easier to link a C program unit into a FORTRAN project.


extern "fortran" ....

C has a lot of other use cases too, of course, but C-style linking is definitely still the lingua franca of multi-language projects.


On the operating systems, where the ABI == C linkage model.

On Lilith for example, you would need to use Modula-2 linkage module. In Native Oberon, the ABI is Oberon based. In Spin it is Modula-3 based and so forth.

You can argue they are all dead, but lets take Windows 8. On the platforms where the only Windows ABI is WinRT like the ARM tablets, the lowest API is COM and the only native code compiler C++.

In this case, your languages need to communicate via the COM bindings, there is no C interop any longer.

Sure you can still use C, but it will be C communicating via the COM API.

This means in the long run, C++ replaces C as the lowest API on Windows, if WinRT is sucessfull.

In Symbian likewise, if you're using some C stuff, you're actually compiling C like code in a C++ compiler, because the ABI and exposed interfaces are all C++ based.

Again, C as lingua franca only works if C is the language exposed by the operating system. Lets not forget there were system programming languages before it, and after it, why should C exist forever?

Reply Parent Score: 2