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: glenn andreas <email@hidden>
- Date: Fri, 10 Feb 2006 13:53:25 -0600
On Feb 10, 2006, at 1:23 PM, Scott Ribe wrote:
I am confused.
Yeah, I think you've misread the question and made it way more
complicated.
I just want a proper class-scoped constant--only visible within the
class
and not susceptible to name clashes with constants in other classes.
[snip]
Given the other off-target responses I've gotten, (and that I checked
documentation before posting) I'm just going to assume that in
Objective-C
there is no notion of a constant with class scope. Seems an odd
omission,
but if that's the way it is, then that's the way it is ;-)
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).
"Sometimes it just bes that way!"
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
Dominogy | Just place all the dominos on the board...
_______________________________________________
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