This is a pretty huge step. C++ support in Clang has always lagged behind, but the Clang internals is all C++ -- as mentioned in the blog it isn't self-hosting yet, just self-building, but this is major step in making Clang a true replacement for GCC.
Compilers revolutions don't happen overnight, but rejoice, you are seeing one happen right now.
I personally can't wait to see systems like OSX & FreeBSD use Clang as their default compilers, which might happen in the next few years.
I personally can't wait to see systems like OSX & FreeBSD use Clang as their default compilers...
Some parts of OS X are already compiled with Clang. Off the top of my head, OpenCL, OpenGL and Xcode are all compiled with Clang now. Also, I think (but can't source) AppleScript Studio is also compiled with Clang. And there's MacRuby that's built on llvm.
I'm happy to see this moment. I don't want to diminish it, but aren't these tools written in a "tasteful subset" of c++, which could mean there are still many missing nooks and crannies?
[+] [-] pquerna|16 years ago|reply
Compilers revolutions don't happen overnight, but rejoice, you are seeing one happen right now.
I personally can't wait to see systems like OSX & FreeBSD use Clang as their default compilers, which might happen in the next few years.
[+] [-] Zev|16 years ago|reply
Some parts of OS X are already compiled with Clang. Off the top of my head, OpenCL, OpenGL and Xcode are all compiled with Clang now. Also, I think (but can't source) AppleScript Studio is also compiled with Clang. And there's MacRuby that's built on llvm.
[+] [-] pohl|16 years ago|reply
[+] [-] congnhutpy|16 years ago|reply