Sean McBride wonders: > I was modernizing some of my code to support NSSecureCoding instead of just > NSCoding and stumbled upon that fact that NSColor and NSImage support only > NSCoding and not NSSecureCoding. Whereas NSURL, NSData, NSArray and > countless others now support NSSecureCoding. > > Is it just that Apple hasn't gotten around to NSColor and NSImage, or is > there some rationale I'm not seeing?
Given my understanding of NSSecureCoding's implications/promises, I'm thinking NSColor and NSImage may have nothing to gain by implementing that protocol. Perhaps the (current) encoded form of those types is only a collection of scalars; object substitution isn't a meaningful concern. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
