Re: loop efficiency & messages
Re: loop efficiency & messages
- Subject: Re: loop efficiency & messages
- From: mmalcolm crawford <email@hidden>
- Date: Wed, 23 Mar 2005 15:53:20 -0800
On Mar 23, 2005, at 11:23 AM, John Stiles wrote:
On Mar 23, 2005, at 11:16 AM, Philip Mötteli wrote:
Also minor changes of just one method, like -[NSString cString]
has been depreciated too.
That example actually proves my point perfectly. cString has been
deprecated forever, because UTF8String is better. But that doesn't
mean cString is going away, because I guarantee that will break a
lot of existing apps (since a lot of programmers don't know about
UTF8String, or prefer cString for whatever reason).
Apple may eventually make it so that newly compiled apps can't use
cString any more. That's happened. But breaking apps that are in
the field, just so they can clean up old functions out of AppKit?
That's just not going to happen. Period.
Please do not make such assertions. Writing "Period" at the and of a
paragraph does not "make it so".
If a method is marked as deprecated, it may indeed go away, whether
or not it breaks existing applications. The only safe assumption to
make when a method is marked as deprecated is that it will at some
stage disappear. To claim otherwise is stupid and misleading.
mmalc
_______________________________________________
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