Re: Objective-C++, class scope constants, name conflicts
Re: Objective-C++, class scope constants, name conflicts
- Subject: Re: Objective-C++, class scope constants, name conflicts
- From: Scott Ribe <email@hidden>
- Date: Fri, 10 Feb 2006 18:39:27 -0700
- Thread-topic: Objective-C++, class scope constants, name conflicts
> Correct - there is no scope introduced by @interface..@end in
> Objective-C(++) (other than the implicit anonymous structure field
> scope for ivars, which doesn't do what you need anyway).
OK. Seems odd from the semantic viewpoint to not allow class-scope
constants. But your message's reference to the anonymous struct made me
realize that it might require a whole new area of implementation effort
compared to the way it is now...
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden