NSObject+NSDictionaryRepresentation.h

#import <Foundation/Foundation.h>

@interface NSObject (NSDictionaryRepresentation)

/**
 Returns an NSDictionary containing the properties of an object that are not nil.
 */
- (NSDictionary *)dictionaryRepresentation;

@end

NSObject+NSDictionaryRepresentation.m

#import "NSObject+NSDictionaryRepresentation.h"
#import <objc/runtime.h>

@implementation NSObject (NSDictionaryRepresentation)

- (NSDictionary *)dictionaryRepresentation {
    unsigned int count = 0;
    // Get a list of all properties in the class.
    objc_property_t *properties = class_copyPropertyList([self class], &count);
    
    NSMutableDictionary *dictionary = [[NSMutableDictionary alloc] initWithCapacity:count];
    
    for (int i = 0; i < count; i++) {
        NSString *key = [NSString stringWithUTF8String:property_getName(properties[i])];
        NSString *value = [self valueForKey:key];
        
        // Only add to the NSDictionary if it's not nil.
        if (value)
            [dictionary setObject:value forKey:key];
    }
    
    free(properties);
    
    return dictionary;
}

@end

nice man... But dictionary is not released :)

@hamdullahshah That's being used in an ARC project.

Oops sorry my mistake :)

pretty cool .. thanx
Would it make sense to add to NSObject something like setValuesFromRepresentation (KVC)? Or would it be against rules to put that feature into something like + initWithRepresentation?