• Choose a category
• All
• Classic-Fiction

@end

In Employee.m, create an instance of the correct class:

- (void)addAssetsObject:(Asset *)a

{

if (!assets) {

assets = [[NSMutableSet alloc] init];

}

[assets addObject:a];

[a setHolder:self];

}

Build and run the program. It should function the same.

You can’t access an object in a set by index because there is no sense of order in a set. Instead, all you can do is ask “Is there one of these in there?” NSSet has a method:

- (BOOL)containsObject:(id)x;

When you send this message to a set, it goes through its collection of objects looking for an object equal to x. If it finds one, it returns YES; otherwise it returns NO.

This brings us to a rather deep question: what does equal mean? The class NSObject defines a method called isEqual:. To check if two objects are equal, you use the isEqual: method:

if ([myDoctor isEqual:yourTennisPartner]) {

NSLog(@"my doctor is equal to your tennis partner");

}

NSObject has a simple implementation of isEqual:. It looks like this:

- (BOOL)isEqual:(id)other

{

return (self == other);

}

Thus, if you haven’t overridden isEqual:, the code snippet is equivalent to:

if (myDoctor == yourTennisPartner) {

NSLog(@"my doctor is equal to your tennis partner");

}

Some classes override isEqual:. For example, in NSString, isEqual: is overridden to compare the characters in the string. For these classes, there is a difference between equal and identical. Let’s say I have two pointers to strings:

NSString *x = ...

NSString *y = ...

x and y are identical if they contain the exact same address. x and y are equal if the strings they point to contain the same letters in the same order.

Thus, identical objects are always equal. Equal objects are not always identical.

Does this difference matter? Yes. For example, NSMutableArray has two methods:

- (NSUInteger)indexOfObject:(id)anObject;

- (NSUInteger)indexOfObjectIdenticalTo:(id)anObject;

The first steps through the collection asking each object “isEqual:anObject?” The second steps through the collection asking each object “== anObject”?

NSDictionary/NSMutableDictionary

As you know, arrays are indexed by a number; it is easy to ask “Give me object 10.” Dictionaries are indexed by a string; it is easy to ask “Give me the object stored under the key favoriteColor.” More precisely, a dictionary is a collection of key-value pairs. The key is typically a string, and the value can be any sort of object. These key-value pairs are not kept in any particular order.

Let’s make a dictionary of executives. The key will be an executive title, and the value will be an instance of Employee. The first employee will be put in the dictionary under @"CEO"; the second under @"CTO". Change your main.m to create and populate the NSMutableDictionary. Then, print out the dictionary of executives. Finally, set the pointer to the dictionary to nil so that you can see the dictionary being deallocated.

// Create an array of Employee objects

NSMutableArray *employees = [[NSMutableArray alloc] init];

// Create a dictionary of executives

NSMutableDictionary *executives = [[NSMutableDictionary alloc] init];

for (int i = 0; i < 10; i++) {

// Create an instance of Employee

Employee *person = [[Employee alloc] init];

// Give the instance variables interesting values

[person setWeightInKilos:90 + i];

[person setHeightInMeters:1.8 - i/10.0];

[person setEmployeeID:i];

// Put the employee in the employees array

[employees addObject:person];

// Is this the first employee?

if (i == 0) {

[executives setObject:person forKey:@"CEO"];

}

// Is this the second employee?

if (i == 1) {

[executives setObject:person forKey:@"CTO"];

}

}

…

NSLog(@"allAssets: %@", allAssets);

NSLog(@"executives: %@", executives);

executives = nil;

NSPredicate *predicate = [NSPredicate predicateWithFormat:

@"holder.valueOfAssets > 70"];

NSArray *toBeReclaimed = [allAssets filteredArrayUsingPredicate:predicate];

NSLog(@"toBeReclaimed: %@", toBeReclaimed);

toBeReclaimed = nil;