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: Thomas Engelmeier <email@hidden>
- Date: Fri, 10 Feb 2006 09:36:27 +0100
On 10.02.2006, at 01:17, Scott Ribe wrote:
Was static const no good? i.e.
class Foo
{
static const int value = 123;
void Fn();
};
That wasn't allowed in C++ for quite a while. I think it was ISO C+
+ that
added it? Thus my comment about getting used to the enum trick.
Actually, it was IIRC added in the 1998 C++ standard but took some
time until the compiler vendors catched up..
Anyway, it only allows POD data types (int, long, ..).
Regards,
Tom_E
_______________________________________________
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