Re: Why not a procedure for retain/release?
Re: Why not a procedure for retain/release?
- Subject: Re: Why not a procedure for retain/release?
- From: "Ben Kennedy" <email@hidden>
- Date: Thu, 4 Nov 2004 19:51:40 -0500
- Organization: Zygoat Creative Technical Services
On 05 11 2004 at 7:19 pm -0500, Mark Patterson wrote:
>Since NSObject properties have to be retained and released in their
>setter methods, I wrote the little procedure replaceProperty
>demostrated below. Is there any reason against doing this sort of
>thing?
Well, the only benefit you gain from that is saving a few characters of
typing. On the other hand, it introduces an extra function call (50%
more overhead). One could argue the code is less clear for the same
reason. If you insist on doing this, maybe a macro would be better (to
avoid the function call).
-b
--
Ben Kennedy, chief magician
zygoat creative technical services
613-228-3392 | 1-866-466-4628
http://www.zygoat.ca
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden