News for hackers. Stuff that matters.
Re:How to Learn to Write iOS Apps by Aqua_Geek on Saturday December 24, 2011 @04:12PM (#3389683)
> track down an example app to hack around with.

Just watch out - as with every language, there is a lot of bad code out there. While I agree with the notion of reading others' code (personally that helps me a lot to learn a new language), I'd go through the Apple-provided sample code before venturing into code of random apps.

Re:How to Learn to Write iOS Apps by phil on Saturday December 24, 2011 @11:44PM (#3390450)
Unfortunately, much of the Apple sample code is also pretty terrible.

Here's one heuristic: if you see any Objective C++ files (*.mm) in the project, you can probably ignore it as an example of good style.

Re:How to Learn to Write iOS Apps by stuartjmoore on Sunday December 25, 2011 @11:22AM (#3391174)
Disagree. Some good libraries are C++, so linking to them requires you to use Obj-C++ (at very least, changing the name to *.mm).
Re:How to Learn to Write iOS Apps by phil on Monday December 26, 2011 @04:31PM (#3393985)
Yeah, I meant things like sample code for plain C frameworks, where the author has just decided "hey, why not do this in Obj-C++ instead of Obj-C." As I recall, many of the AudioToolbox examples are like this.

Didn't mean to imply that there's no place for Obj-C++, just that it's not good style if you don't actually need it (like to wrap a C++ lib).

Re:How to Learn to Write iOS Apps by Aqua_Geek on Monday December 26, 2011 @01:30PM (#3393513)
The number of iOS examples using Objective-C++ is pretty minimal, IIRC.