8 ms·
Poll: What compiler do you use for iOS development?
- migueldeicaza 15y agoMonoTouch
- twsted 15y agoNo downvotes because Miguel... we love you (and Mono et al. are really good pieces of technology)
- rickharrison 15y agoI use LLVM mainly for the ability to put ivars in a class extension. I.E. @interface MyClass() { MyNewIvar *ivar } @end
- seurahepo 15y agoThat is rather nifty, I think they can nowadays also be defined in the @implementation of a class. I am not using ivars much, almost everything is a property. Too bad Apple scrapped the automatic synthesize feature.
- bronxbomber92 15y agoI use Clang (IMO you should rename LLVM Compiler to Clang). I find putting ivars in my implementation files keeps my headers extremely clean.
- jamesjyu 15y agodone
- eridius 15y agoClang is the future. GCC is obsolete, and LLVM-GCC was just a temporary technology to help migrate from GCC to Clang. All new projects should absolutely be using Clang now, and any old projects that haven't already switched should seriously consider doing so.
- psychotik 15y agoIs switching as simple as changing the project config to use the new compiler, or is code migration/change needed?
- jamesjyu 15y agoYou'll probably get some minor warnings here and there due the differences in the Parser. But in my experience, it's been relatively painless.
- eridius 15y agoDepends on your code. For well-written code that conforms to standards, switching the compiler may be completely pain-free. For most code, you'll probably get a few warnings (since Clang's default warning set is different than GCC's). In rare occasions you'll hit an actual behavioral difference between GCC and Clang, but you'll typically only find those where you're already writing non-standards-compliant code. Also, if you do get some warnings when you switch to Clang, I would recommend fixing them rather than trying to squelch the warnings. Clang's warning set is pretty well-thought-out and things it flags as warnings are typically indicative of bad code (or coding practices).
- dman 15y agoYou might want to clarify that your statements are within the iOS / OSX context. Calling gcc obsolete in other contexts might not be entirely accurate.
- eridius 15y agoYou have a good point, though this entire post is in the context of iOS. But yes, GCC is only obsolete for OS X/iOS development.
- extension 15y agowhy?
- 15y ago
- ericflo 15y agoMisclicked on LLVM-GCC, meant to click on LLVM Clang.
- zdw 15y agoJust out of curiosity, anyone know of a good CLI xcodebuild cheatsheet or reference? I'm used to make/rake for most things, and would love NOT to have to load GUI Xcode every time I needed to rebuild an app...
- e28eta 15y agoI think you're just looking for the man page. There are blog posts out there showing how to set up CI builds, which will also get you started, but the man page isn't too long and is the authoritative reference for what xcodebuild will do.
- caycep 15y agogezundheit!
- kristianp 15y agoGambit Scheme.
- deleted 15y ago[deleted]
- ctoshok 15y agocoffeekit!