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: Chris Hanson <email@hidden>
- Date: Fri, 10 Feb 2006 23:49:55 -0800
On Feb 10, 2006, at 11:23 AM, Scott Ribe wrote:
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.
Objective-C doesn't have any notion of a "class-scoped constant"
because a class doesn't define a scope or namespace, just a structure
and the means to operate on it. It defines the layout of instances
(the instance variables), the messages that the class and its
instances respond to, and the methods used to respond to those
messages. That's it.
-- Chris
_______________________________________________
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