On Oct 28, 2008, at 00:19, Jean-Nicolas Jolivet wrote:

Is it ok to bind my column to a property that is, in fact, not a property but just a method that returns a string... or should I create an actual instance variable "NSString *fileName" with a regular getter and setter....?

A property *is* just a method (or, if readwrite, a pair of methods -- the getter and the setter). The instance variable, if there is one, is "merely" an implementation detail within the class. Some properties don't use an instance variable (NSString's lastPathComponent property almost certainly doesn't, for example). Some properties (like your "fileName") use an instance variable, but compute a value from it.

Furthermore, assuming that your File class has both filePath and fileName properties, then your fileName implementation:

        return [filePath lastPathComponent];

might alternatively be:

        return [self.filePath lastPathComponent];

If you get the difference, you're home free, conceptually. (The 2nd one extracts the file name from your filePath property, without any assumption about how the property is implemented. The 1st one uses a convenient instance variable that happens to contain the information you want. Either approach is fine in this case, but in more complicated cases, it's important to distinguish between the value of the property and the value of some variable.)

Finally, you also need to pay attention to KVO compliance. Assuming your filePath property is compliant (meaning that changes to it produce the proper KVO notifications), your fileName property isn't (unless the filePath never changes in a File object after it is initialized, in which case the question is moot).

HTH
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to