Question

I am currently using the following conventions

- (id) initWithName:(NSString *) name;

+ (NSString *) aliasForName:(NSString *) name

- (void) method

- (void) methodWithApple:(NSString *) apple andOrange:(NSString *) orange
andMango:(NSString *) mango

- (void) statusWasChanged:(id)sender

Do you have a better style for the above methods?

Thanks

Answer 1

Coding Guidelines for Cocoa is a great resource for answering any naming convention questions. My answer is as much as possible based off of this.

Init Method

The init method looks good.

- (id) initWithName:(NSString *) name;

Class Method

The class method looks good.

+ (NSString *) aliasForName:(NSString *) name

Class methods can also be used to instantiate an instance of an object. In this instance, Apple’s API’s generally have the method start with the name of the class like UIButton‘s buttonWithType: method that has the signature:

+ (id)buttonWithType:(UIButtonType)buttonType

Instance Methods

Good resource for coding conventions for methods can be found under General Rules.

The following method should drop the "and"s:

- (void) methodWithApple:(NSString *) apple andOrange:(NSString *) orange
andMango:(NSString *) mango  // BAD

Don’t use “and” to link keywords that are attributes of the receiver.

- (int)runModalForDirectory:(NSString *)path file:(NSString *) name types:(NSArray *)fileTypes; right

- (int)runModalForDirectory:(NSString *)path andFile:(NSString *)name andTypes:(NSArray *)fileTypes; wrong

The signature should look more like the following:

- (void) methodWithApple:(NSString*)apple orange:(NSString*)orange
mango:(NSString*)mango  // GOOD

Delegate Methods

Lastly, I think there are a couple improvements that could be made on what appears to be a delegate method:

- (void) statusWasChanged:(id)sender  // Not horrible, but not ideal

First improvement is to add the class name to the method.

Start the name by identifying the class of the object that’s sending
the message:

- (BOOL)tableView:(NSTableView *)tableView shouldSelectRow:(int)row;
- (BOOL)application:(NSApplication *)sender openFile:(NSString *)filename;

Second improvement is to use "DidChange" instead of "WasChanged".

Use “did” or “will” for methods that are invoked to notify the
delegate that something has happened or is about to happen.

- (void)browserDidScroll:(NSBrowser *)sender;
- (NSUndoManager *)windowWillReturnUndoManager:(NSWindow *)window;

Third improvement is strongly casting the sender parameter. I don’t have documentation to support this, however all examples provided in the examples exude this behavior. Notice the (NSBrowser*)sender and (NSWindow*)window in the above code sample taken straight from the apple docs.

With this in mind, the delegate method should look more like:

- (void) senderClassNameStatusDidChange:(SenderClassName*)sender  // Good

If the sender were a Person object it would look like:

- (void) personStatusDidChange:(Person*)sender  // Good

A word of caution is that you shouldn’t always use “did” in delegate methods.

Although you can use “did” or “will” for methods that are invoked to
ask the delegate to do something on behalf of another object, “should”
is preferred.

- (BOOL)windowShouldClose:(id)sender;