There are a couple of points I want to comment on:
I'm afraid I don't understand that assertion at all. What does this
have to do with binary compatibility? Why did it *not* break
compatibility in the move from 10.4 (in which new does not invoke
alloc by default) to 10.5 (in which it does)?
Because this is an implementation detail.
So in Leopard, as you say zones have fallen out of recommended
practice
I'm guessing, but perhaps the assumption made on Apple's part is that
if you are linking against the 10.5 SDK then your are more then likely
using GC and zones are irrelevant? AFAIF zones can be used to improve
alloc/dealloc performance, i.e they can be setup such that the cost of
dealloc'ing a large group of temporary objects is very low by simply
removing references to their heap section allowing immediate reuse
without the dealloc tear down cost. Correct me if I'm wrong.
Keith
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
