Re: Xcode 3.2.3: cannot pair a synthesized setter/getter with a user defined setter/getter
Re: Xcode 3.2.3: cannot pair a synthesized setter/getter with a user defined setter/getter
- Subject: Re: Xcode 3.2.3: cannot pair a synthesized setter/getter with a user defined setter/getter
- From: David Brown <email@hidden>
- Date: Fri, 18 Jun 2010 13:39:44 -0700
>> IMHO, that's a bad comparison and therefore a bad decision. It does not take into account the crucial statistics about how often you actually need it, which is really very rarely for most situations, and you should know when you do anyway. So you have two rare situations, namely when performance becomes a big issue and when you actually access properties from multiple threads. These two cancel each other out, which leaves you with the general argument that atomic is generally unnecessary therefore bad. Moreover, it gives you the non-intuitive warnings like what's discussed in this thread. Just my opinion.
In my experience, many programmers (perhaps the sort who are NOT reading this list) do not always understand when they have suddenly entered into the land of multiple threads. For instance, Java servlets are multithreaded, and in a previous life I have spent many billable hours cleaning up after that.
With GCD and blocks, it is easier than ever to create race conditions. If you have enough of a clue to understand where you are multithreaded and where you are not (and know that no one else will ever use your class in a multithreaded situation), then you can turn it off quite easily.
The decision that they made leads to more solid code without much work. Worrying about performance issues before they are actually an issue is exactly the sort of pre-optimization that should be avoided. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden