|
| From: | Doug Simons |
| Subject: | [bug #25370] NSUserDefaults doesn't copy mutable objects |
| Date: | Wed, 21 Jan 2009 05:55:34 +0000 |
| User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_4_11; en) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 |
URL:
<http://savannah.gnu.org/bugs/?25370>
Summary: NSUserDefaults doesn't copy mutable objects
Project: GNUstep
Submitted by: theeggcamefirst
Submitted on: Wed 21 Jan 2009 05:55:33 AM GMT
Category: Base/Foundation
Severity: 3 - Normal
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
The NSUserDefaults method setObject:forKey: apparently just retains the
object rather than copying it. This leads to some unexpected behavior if the
object is mutated after calling setObject:forKey: but before calling
synchronize -- namely, the wrong value is stored in the defaults database.
This is different from Cocoa's behavior.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25370>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |