Style Guide

Herein lies some conventions used throughout the OpenEmu codebase.

This list is by no means exhaustive and quite prototypal as of yet.

Whitespace

• Braces on their own line

- (void)method
{
}

• Pointer declaration

NSString *myString;

• Block argument list and types on their own line

int (^blk1)(int) =
^ int (int v)
{
};

[someDictionary enumerateKeysAndObjectsUsingBlock:
 ^ (id key, id obj, BOOL *stop)
 {
 }];

• Caret and curly brace on previous line when there is no block parameters

dispatch_async(^{
    // My code
});

• Space between caret and block's return parameter list (when no return data-type is specified)

^ (id key, id obj, BOOL *stop)

• Space between caret and block's return data-type and space between block's return data-type and parameter list

^ int (id key, id obj, BOOL *stop)

• Use 4 spaces instead of tabs

@interface SomeClass
{
    int ivar;
}

• Class ivars and properties should be aligned

@interface SomeClass
{
    int       someValue;
    BOOL      shouldCloseFile;
    NSString *description;
}

@property(strong) IBOutlet OELibraryController *libraryController;

@property(nonatomic, strong) NSViewController  *currentContentController;
@property(nonatomic, strong) NSViewController  *defaultContentController;
@property                    BOOL               allowWindowResizing;

@property(copy) NSArray *deviceHandlers;
@property(copy) NSArray *coreList;

@end

• For NSArray and NSSet variadic list, place each value on its own line

NSArray *someArray = [NSArray arrayWithObjects:
                      @"value1",
                      @"value2",
                      nil];

NSSet *someSet = [NSSet setWithObjects:
                  @"value1",
                  @"value2",
                  nil];

• For NSDictionary place each value and key pair on the same line

NSDictionary *someArray = [NSDictionary dictionaryWithObjectsAndKeys:
                           @"value1", @"key1",
                           @"value2", @"key2",
                           nil];

Naming conventions

• Class names are CamelCased

@implementation SomeClass

• Private categories described by empty category, implementation methods placed within main @implementation block

@interface SomeClass()
@end

• Private methods prefixed with OE_

- (void)OE_privateMethod:(BOOL)value;

• Use YES and NO

Ordering

• Implementation classes should follow this general ordering guideline:

  1. @synthesize
  2. +initialize
  3. -init
  4. -dealloc
  5. Class Methods (+someMethod)
  6. Instance Methods (-someMethod)
  7. Delegate Implementation
  8. Setters / Getters

• Order methods by tasks

• Private methods should be close to the public methods that call them

Objective-C 2.0

• avoid 'dot-syntax'

Miscellaneous

• Perfer MAX and MIN macros over if statements. for example:

value = MAX(someCalculations, someValue);

instead of

value = someCalculations;
if(value < someValue) value = someValue;

• There is no need to use conversion functions like NSRectFromCGRect or NSPointToCGPoint to convert NS-datatypes to CG-datatypes and vice versa.

Code sample

Here you can see a sample class:

#import "someheader.h"

@interface SomeClass
{
    int ivar;
}

- (void)method;

@end

@interface SomeClass ()

- (void)OE_privateMethod;

@end

@implementation SomeClass

- (void)OE_privateMethod
{
    // do things
}

- (void)method
{
    if(booleanValue && obj != nil)
    {
        do
        {
            [self OE_privateMethod];
        } while(value > 0);
    }

    while(value < 10)
    {
    }
    
    void (^blk)(void) =
    ^{
        // do things
    };
    
    int (^blk1)(int) =
    ^ int (int v)
    {
        // do things
    };
}

@end

More

For more information read Apple's Coding Guidelines for Cocoa, since the project adheres to these.