Re: Proper use of #define to aid in compile-time checking of strings (was KVC and KVO for arrays)
Re: Proper use of #define to aid in compile-time checking of strings (was KVC and KVO for arrays)
- Subject: Re: Proper use of #define to aid in compile-time checking of strings (was KVC and KVO for arrays)
- From: Jonathan Dann <email@hidden>
- Date: Sat, 16 Feb 2008 16:21:15 +0000
On 15 Φεβ 2008, at 5:52 ΜΜ, John Dann wrote:
If I want to change the name of the NSOutlineView column to which
the #define statement referrs at some time in the future, I'll have
to change both, and likely forget one. Is there any way around
this without placing the #define in my NSDocument subclass's .h file?
You could define a constant method (like in SmallTalk) in your main
class, that your categories can call e.g.:
- (NSString *) sourceListColumnID {
return @"sourceListColumn";
}
This can be called from your categories and you won't have to
duplicate your constants
Of course! Isn't it embarrassing when one can't see the wood for the
trees!
Thanks again!
Jon_______________________________________________
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