First Glance at Objective-C and the iPhone SDK (by a Java and C Developer)

Re:First Glance at Objective-C and the iPhone SDK (by a Java... by donmcc on Wednesday January 26, 2011 @12:50PM (#2144106)

With gc enabled, [autoreleasePool drain] asks the gc to run (IIRC), with gc disabled, it releases everything currently owned by the pool. Even on the Mac, you may still want to build your app without gc for performance reasons, and Apple gives you that option.

I'm sure we'll see gc on iOS devices eventually, but it's probably too memory hungry to be practical on the phone right now.

[ Parent | on HN ]

Re:First Glance at Objective-C and the iPhone SDK (by a Java... by chc on Wednesday January 26, 2011 @03:12PM (#2144914)

The drain method releases the pool itself — it's precisely equivalent to release. This does release the objects in the pool as well, but a lot of people seem to think that drain leaves the pool valid. (The reason it was introduced is so the same method could be used in non-GC and GC code, where release is turned into a noop.)

[ Parent | on HN ]

Re:First Glance at Objective-C and the iPhone SDK (by a Java... by rst on Wednesday January 26, 2011 @02:32PM (#2144684)

Either that, or the objC gc isn't ready for a phone-constrained environment yet. Android seems to manage OK, but they put in a lot more up-front work into making it viable there.

[ Parent | on HN ]