On Sat, Jun 7, 2008 at 11:24 PM, Hamish Allan <[EMAIL PROTECTED]> wrote:
> Sure, you could design NSData differently to mask a design problem in > GC. But GC won't be easier to use than retain/release/autorelease > without simple rules like "if you declare it on the stack, it's in the > root set, regardless of whether the compiler optimises it into a > register". Sorry to reply to myself, but I just remembered that pointers in registers are also in the root set! That said, I don't think it changes the substance of my proposal: that stack variables (i.e. variables semantically placed on the stack by the programmer) should remain in the root set until they are out of scope (i.e. semantically no longer in the current stack frame). Hamish _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
