@Ben: I find it odd you presented the performance issue as primary and the horrendous game-ending memory leak as a footnote.
It's a good point, but I guess I see Core Video as relatively specialized and already working in very performance-sensitive areas. Using CoreGraphics APIs is far more common, even in many simple apps. But stepping back, I see what you mean.
I haven't moved to Leopard yet, but can't you do a GC project and still choose to manually memory-manage specific objects?
Not really. You can set object-specific parameters for the collector, but they're all still garbage collected. The retain, release and autorelease methods become no-ops (for all frameworks) when garbage collection is on. CF-style objects have different rules, though.
by Scott Stevenson — Nov 29
It's a good point, but I guess I see Core Video as relatively specialized and already working in very performance-sensitive areas. Using CoreGraphics APIs is far more common, even in many simple apps. But stepping back, I see what you mean.
I haven't moved to Leopard yet, but can't you do a GC project and still choose to manually memory-manage specific objects?
Not really. You can set object-specific parameters for the collector, but they're all still garbage collected. The retain, release and autorelease methods become no-ops (for all frameworks) when garbage collection is on. CF-style objects have different rules, though.