What you're describing appears to be a subclass However, in Objective-C, you have the simpler option of defining a category on an existing class to add the functionality you want.
What you're describing appears to be a subclass. However, in Objective-C, you have the simpler option of defining a category on an existing class to add the functionality you want.
Perfect! Exactly what I was looking for. So I've created the .
M and . H, But I still don't know how I should handle the following: EKEvent has a few objects, such as: NSDate *_dateStamp; So when I define - (void)encodeWithCoder:(NSCoder *)coder, from Apple Documentation (regarding custom subclasses) I see that I should put: coder encodeObject:dateStamp forKey:@"dateStamp"; of course, XCode complains that the "dateStamp" object does not exist (because it is not declared in the Category). Do I just re-declare?
Would there be a problem with that (I assume there would)? – Daniel Amitay Jul 13 '10 at 1:08 The name of the field is _dateStamp, not dateStamp, and as long as you're importing the header, it should be visible. However, I would be careful not to run afoul of implementation details that might change in the future.
– Chuck Jul 13 '10 at 1:25.
What you're describing appears to be a subclass .
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.