Created
August 8, 2011 20:17
-
-
Save mikeash/1132620 to your computer and use it in GitHub Desktop.
Namespaced constants in C
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#import <Foundation/Foundation.h> | |
// .h file | |
struct MyConstantsStruct | |
{ | |
NSString *foo; | |
NSString *bar; | |
int baz; | |
}; | |
extern const struct MyConstantsStruct MyConstants; | |
// .m file | |
const struct MyConstantsStruct MyConstants = { | |
.foo = @"foo", | |
.bar = @"bar", | |
.baz = 42 | |
}; | |
// user | |
int main(int argc, char **argv) | |
{ | |
[NSAutoreleasePool new]; | |
NSLog(@"%@ %@ %d", MyConstants.foo, MyConstants.bar, MyConstants.baz); | |
} |
I guess I assumed 'dynamic arrays' in c99 would let me use them in structs. What's the enum idea? Thanks.
Variable length arrays are only available for local variables. Otherwise the compiler needs to know sizes at compile time.
Enum constants look like this:
enum
{
kMyConstant = 42,
kMyOtherConstant = 99
};
Of course, since enums can only be integers, this construct can only be used for integer constants.
Oh cool, I didn't know they could be assigned values. Thanks Mike, good tip. :)
ARC does not allow it... :(
ARC does allow it, but unfortunately you must put __unsafe_unretained
before all of the object pointer struct members to make ARC happy.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That is true, however the same is true of a simple global variable constant, nothing to do with the struct. The only way to avoid this would be to use
#define
orenum
instead of a "real" global variable constant.