On Sun, Feb 28, 2010 at 6:16 PM, Eagle Offshore <[email protected]> wrote: > Really? This is a problem somehow?
Yes. You can either provide an object or nil. You gave it an object it didn't like. > NSManagedObject couldn't just take the hint and go with nil? Would you rather an API based on "taking hints" or an API based on documentation? You can either provide nil or a string. Why should NSManagedObject assume that an object of a certain class should get special treatment? Should it do the same for NSValues wrapping an integer 0? What about NSNoSelectionMarker or NSNotApplicableMarker? --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
