Jason Coco wrote:
NSMutableString *str = [[NSMutableString alloc]
initWithCapacity:someAssumedCapacity];
/* do stuff */
[str release];
Is that actually guaranteed to release the string *right now*? I only
ask because I seem to recall a message a couple of months ago about a
more complicated object where it appeared that the initializer did a
retain/autorelease on the object so it ended up in the autorelease pool
before you even got hold of it. That was not an object obtained from a
convenience method either IIRC, it was a [ [ SomeClass alloc ]
initConstructorOfSomeSort ] call.
Unlikely the case with NSMutableString I'd think, but perhaps for other
things.
The local autorelease pool version I'd think is guaranteed to work.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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]
