Re: [Pyobjc-dev] NSArray removes KeyValueCoding.kvc wrapper?
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2006-09-24 17:04:58
|
On Sep 24, 2006, at 6:47 PM, James R Eagan wrote: > Ahh, that makes some sense, but isn't it a bit of overhead to add a > wrapper instantiation on top of every key value lookup? > > What I ended up doing was to keep a lookup dictionary that caches the > kvc wrappers. The kvc wrappers are pretty lightweight. You don't have to use them anyway, it is just a convenience to get nicer looking code, so if speed is a concern you can use the KVC methods directly (valueForKey: and friends). I want to do some experimentation to use KVC everywhere, just like in NSManagedObject. That is, anObject.foo fetches the value of a key and anObject.bar = 42 sets a key using KVC. There is one major problem here: the setter method in Objective-C doesn't have a prefix in its name, which causes a problem in Python because methods and attributes share a single namespace and we therefore can't know if 'someObject.foo' is meant to be a reference to a method or the value of an instance variable. Ronald |