Re: From Panther to Tiger
Re: From Panther to Tiger
- Subject: Re: From Panther to Tiger
- From: Bob Ippolito <email@hidden>
- Date: Mon, 16 May 2005 15:54:20 -0400
On May 16, 2005, at 3:14 PM, Matt Neuburg wrote:
On Mon, 16 May 2005 04:29:42 +0200, Andreas Mayer
<email@hidden> said:
Am 15. Mai 2005 um 23:07 Uhr schrieb Gerriet M. Denkmann:
Does there somewhere exist a list of things which are different in
Tiger
You may want to start here:
http://developer.apple.com/referencelibrary/index-rev-date.html
Or not. I certainly didn't find anything in the release notes or in
the
reference that explained why one of my apps broke. The mutability
behavior
of a dictionary returned using NSDictionary
dictionaryWithContentsOfFile
changed, and I don't know why. It wasn't hard to work around but it
wasn't a
pleasant surprise either.
Well, does it REALLY surprise you that when you ask an immutable
container class to load itself from disk, you will get an immutable
container back? If you send the same message to NSMutableDictionary,
you should get mutable containers back. Since the only way to see if
a type is mutable or not is to mutate it, they didn't break any API
contract since sending those messages to immutable containers would
be invalid.
This was a bug in your code, not Apple's.. their code was "correct"
before, because if you treated them like immutable containers they
wouldn't change.. they simply changed the implementation to enforce
correct behavior (and increase performance, presumably). I don't see
why they should document every case of "this broken code used to
work, by accident, but now doesn't". Perhaps they didn't even know,
since they were simply making ostensibly correct behavior more
correct, not necessarily fixing a bug.
-bob
_______________________________________________
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