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: Nick Toumpelis <email@hidden>
- Date: Fri, 15 Feb 2008 23:23:52 +0200
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.
Nick
_______________________________________________
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