Re: Switching from GCC to Clang, any downsides?
Re: Switching from GCC to Clang, any downsides?
- Subject: Re: Switching from GCC to Clang, any downsides?
- From: Jens Alfke <email@hidden>
- Date: Tue, 8 Sep 2009 07:38:21 -0700
On Sep 8, 2009, at 3:09 AM, Markus Spoettl wrote: I totally understand and agree, Apple should be the one releasing software built with Clang.
In Apple's defense, switching the compiler version used by Mac OS X is a huge undertaking — you can't just flip the switch because there's always something that will fail to build on the first attempt, and you don't want to break the whole OS build. So they have to set up a parallel build, and notify people whose components fail, who then have to set up that same environment and fix their problems and check them in (maybe on a branch)...
It's definitely not something you want to do more than once per OS release (and it looks like Apple already switched from GCC 4.0 to 4.2 in 10.6), and you want to do it as early as possible in the release cycle, and of course you want to make sure the compiler is rock solid before you start. I'm sure Clang wasn't ready back in early 2008.
—Jens |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden