I cant help but think the preferable way Objective C should would is
to send a release automatically to the receiver of a product of itself.
inputString = [inputString myMethod];
Its fairly clear in this situation that the original 'inputString' is
not wanted and needs to die, and would seem like a more sensible way
for the compiler to work as I struggle to think of a situation where
the old value serves any perpose, being that it is now orphaned and
useless.
Hence my confusion on the matter.
On 6 Feb 2009, at 03:17, Scott Ribe wrote:
So, how do I keep a copy hanging around AND kill the mysterious new
copy then (which shares the same name as the old one presumably)?
2 pointer variables...
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
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 arch...@mail-archive.com
