| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Thanks, and to Shawn for the same suggestion. It's a pragmatic solution I can deal with.
A little inner voice insists on asking, though, how we know some future version of the compiler might not optimize '[data self]' upwards before the loop, if it decides that nothing inside the loop references anything non-local:
NSData* data = <get it from somewhere>; const unsigned char* bytes = [data bytes]; NSUInteger count = [data length]; NSUInteger largestByte = 0; for (NSUInteger i = 0; i < count; i++) largestByte = MAX (largestByte , bytes [i]); [data self];
TBH, I don't see any real solution without making the compiler aware of the GC consequences of its optimizations.
b.bum
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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 Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden This email sent to email@hidden
| References: | |
| >Garbage collector vs variable lifetime (From: Quincey Morris <email@hidden>) | |
| >Re: Garbage collector vs variable lifetime (From: Bill Bumgarner <email@hidden>) | |
| >Re: Garbage collector vs variable lifetime (From: Ricky Sharp <email@hidden>) | |
| >Re: Garbage collector vs variable lifetime (From: Bill Bumgarner <email@hidden>) | |
| >Re: Garbage collector vs variable lifetime (From: Quincey Morris <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.