Re: NSForegroundColorAttributeName without AppKit
Re: NSForegroundColorAttributeName without AppKit
- Subject: Re: NSForegroundColorAttributeName without AppKit
- From: Ken Ferry <email@hidden>
- Date: Mon, 1 Mar 2010 21:41:02 -0800
On Mon, Mar 1, 2010 at 9:19 PM, Graham Cox <email@hidden> wrote:
>
> On 02/03/2010, at 4:00 PM, Ken Ferry wrote:
>
> > When you use a symbol like NSForegroundColorAttributeName, a reference to
> the symbol is embedded in your binary, not the value. So it could possibly
> change.
> >
> > Barriers to this would be (1) people persisting attribute
> dictionaries,[...] (1) might, it's hard to say.
>
>
> What about archiving an NSAttributedString to a file? Wouldn't the constant
> string get archived as its value? Then if the symbol changed there would be
> a mismatch between the archive and what the library would be expecting, and
> the saved object wouldn't work correctly.
>
NSAttributedString controls its own archive format and can handle changes.
I don't think this is that likely to change. I also think that reasoning
about exactly how far you can push without having compat problems is kind of
a losing exercise. :-) It's really much nicer to stick to stuff that
everyone agrees is in the supported interface.
-Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden