Re: Sending a build message less severe then #warning
Re: Sending a build message less severe then #warning
- Subject: Re: Sending a build message less severe then #warning
- From: Gwynne Raskind <email@hidden>
- Date: Thu, 28 May 2009 14:06:39 -0400
On May 28, 2009, at 11:13 AM, Sean McBride wrote:
Which is a painful problem for those of us who want to use a
compiler
that's not five years old... You simply *can't* use 4.3, 4.4, or
4.5 for
OS X (or iPhone) development.
Am I missing something or doesn't the latest Xcode give you 4.2 as an
option ? Still old but not as bad as 4.0...
You're right. And 4.2 is 'only' 2 years old:
<http://gcc.gnu.org/gcc-4.2/>
Though Apple's fork surely has changes more recent. It's just
annoying
that there is a fork, and that changes from one take time to get to
the
other (if at all). I suspect that's what Gwynne's comment was about.
1) Yes, 4.2 is "only" 2 years old, but it's still well behind the times.
2) You can't use 4.2 for iPhone dev, only 4.0.
3) Apple's forks are so far behind because they've made so many mods
to the base GCC
4) They've made so many mods to the base GCC because they do things so
fundamentally differently from every other OS out there; the *Windows*
port of GCC is less littered (to my knowledge).
5) Apple could still keep up with mainline GCC if they had done at
least some of their mods as patches which were contributed more
consistently upstream to the FSF version.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."
_______________________________________________
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