Objective-C contstants key naming

Question

I'm little bit confused about constants naming.

kName
NameKey
NAME_KEY

Definitely usage of these fashions?

score 2 · Answer 1 · answered Jan 07 '14 at 12:52

2

According to Coding Guidelines for Cocoa, constances created with const shoul look like this:

The format for const constants is exemplified by the following declaration:

const float NSLightGray;

To see guidelines click here

answered Jan 07 '14 at 12:52

Apan

score 1 · Accepted Answer · answered Mar 07 '11 at 15:41

I suggest to pick your own project or company prefix (like NS or AV above) and stick with it. So, if your prefix is AB:

Apple uses different style depending, I guess, on who wrote the project and when was it written.

score 0 · Answer 3 · answered Mar 07 '11 at 15:23

0

kName is used for string or variable constants. NAME_KEY is used for #define constants.

answered Mar 07 '11 at 15:23

Michaël

That doesn't seem right, look at AV Foundation Error Constants: "NSString *const AVErrorDeviceKey;" for example, they are not prefixed. – Nick Weaver Mar 07 '11 at 15:30
AV is the prefix of the framework, but in your code, your constants are never named like that. – Michaël Mar 07 '11 at 15:34

score 0 · Answer 4 · edited May 23 '17 at 11:55

0

kName is Apple style, while NAME_KEY is alot more widespread among other languages. Doing a lil more research: k is hungarian notation

edited May 23 '17 at 11:55

Community

answered Mar 07 '11 at 15:28

Nick Weaver

score 0 · Answer 5 · answered Mar 07 '11 at 16:21

0

I always use the third style coming from a mainly C background, although I will usually put a prefix on them for frameworks e.g.

NSString* const JP_NAME_KEY = @"name";

answered Mar 07 '11 at 16:21

JeremyP

score 0 · Answer 6 · answered Mar 07 '11 at 16:28

there are a few visible 'cultures' in naming constants across the libraries.

I typically declare constants quite literally, using upper Camel with underscores to separate the longer names:

it's verbose, but it avoids clashes, and it's really clear when the constant applies only to a certain scope, type, library, or other context.

whatever you settle on, just make sure it's consistent.

6 Answers6