Re: loop efficiency & messages
Re: loop efficiency & messages
- Subject: Re: loop efficiency & messages
- From: Philip Mötteli <email@hidden>
- Date: Wed, 23 Mar 2005 20:16:19 +0100
Am 23.03.2005 um 19:45 schrieb John Stiles:
On Mar 23, 2005, at 10:34 AM, Thomas Davie wrote:
On Mar 23, 2005, at 6:26 PM, John Stiles wrote:
On Mar 23, 2005, at 10:00 AM, Philip Mötteli wrote:
So IMHO, the reason, why KVC is looking also into the "get"
version, is due to historic reasons and is definitely not good
coding style. Apple might optimize this case away at any time.
Nope. Once it's documented, it isn't changing. They can't break
shipping apps.
Um, no, deprecated code is free to disappear at any time. Why do you
think you can't create System 7's open/save dialogs any more? It
usually won't disappear because it tends to upset developers - but
you should never rely on it always being there.
What?!?
Bull.
The NSUrl system has been completely rewritten as far as I know. Is the
old NSUrl documentation still available in Apple's most recent API
documentation? And if yes, will it still be in Tiger? I don't think so.
NSUrl is just an example. There are others. Also minor changes of just
one method, like -[NSString cString] has been depreciated too.
Anyway, sometimes things are marked as depreciated, some times later
they disappear from the documentation and some years later, they also
disappear from the library. Sometimes, they start to print a message to
stdout, so that when it's called, you see in your console, that you
shouldn't have too.
But in any case, only because something has been documented doesn't
eternalize it.
Phil
_______________________________________________
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