Linked by Thom Holwerda on Mon 18th Oct 2010 21:54 UTC
Thread beginning with comment 445970
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2008-01-09
If you focus on Objective-C only projects you get the almost full benefits of Clang for iOS code right now as Clang is a first citizen choice in terms of code compiled for iOS. Whenever it finds code it cannot work well with (like C++ and Objective-C++ code, it goes back to LLVM-GCC).
.
You get all of what is outlined in that link minus some kinks with @synthesize by default which, for now, still requires you to both declare the @property as well as call the @synthesize directive for that property, but you are free from having to also write the i-var manually in the class declaration too (in addition to the @property statement and the @synthesize one).
I personally only use Clang right now (Xcode 3.2.5) and I ahve not had major problems with it