| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Frankly, the whole mutable/immutable thing seems confusing at times. ForFor the same reasons that you'd specify a starting capacity when creating a hash table, or call reserve on a vector, etc. Everything will behave the same, but fewer trips into the allocator and fewer memcpy's. This might not be a significant win for some types of code, but for others it may be quite important.
example, what's the point of specifying a capacity when creating a mutable
CF object? I've never been able to detect a performance different when
specifying a maximum capacity. Do the immutable variants offer any
advantages over their mutable counterparts?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/email@hidden
| References: | |
| >Re: CFMutableStringRef creation question (From: Laurence Harris <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.