RE: XCode not releasing nsstring
RE: XCode not releasing nsstring
- Subject: RE: XCode not releasing nsstring
- From: Oliver Donald <email@hidden>
- Date: Wed, 12 Nov 2003 13:21:37 -0000
>
As the other people said, [x release] does not change the address that "x"
>
There is an idea... I am not sure about filing an enhancement request on
it,
>
since I am not quite sure whether it would be good or bad, but if some
basic
>
object (NSObject, or even "lower") would take care of automatically
changing
>
its pointer numeric value when de-allocated, it would have saved some
people
>
some hair.
I thought about adding that as a categroy or something ages ago, but I don't
think there si anyway to do it. I assume what you mean is that, when you
release an object, you want the release method to set the refering pointer
to nil, or some other value? But then you need to give the release method a
pointer to the location in memory of the pointer that pointed to the object
you are releasing. Does that make sense? ;) Try writing the new release
method and you'll see what i mean :) You would have to do it like this:
[myObject releaseFrom:&myObject];
or something like that. I assume thats what you meant, apologies otherwise!
Cheers,
Oli
DISCLAIMER: The information contained in this e-mail is confidential and may
be privileged. It is intended for the addressee only. If you are not the
intended recipient, please delete this e-mail immediately.
The contents of this email must not be disclosed or copied without the
sender's consent. We cannot accept any responsibility for viruses, so please
scan all attachments.
The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the company. The company does
not take any responsibility for the views of the author.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.