On Jul 22, 2008, at 9:07 PM, Graham Cox wrote:
- (void) leakLikeABastard:(NSString**) aString
{
*aString = @"new string";
}
There's nothing about returning an object pointer by reference that's
inherently prone to leaking. The more likely problem is in the caller
of such a method. If the caller supplies the address of a variable
which already holds a strong reference to an object, then passing that
variable by reference to this method would cause the caller to lose
track of its pointer. It would thus be unable to later release its
strong reference, causing a leak.
Cheers,
Ken
_______________________________________________
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]
