Follow-up Comment #2, bug #22565 (project gnustep):
I've just been reworking all the default keypath methods to operaate
recursively the way MacOS-X appears to do. So I'm worried by the comment:
To the requested feature I believe we need to replace the implementation of:
else
{
NSString *key = [keyPath substringToIndex: r.location];
NSString *path = [keyPath substringFromIndex: NSMaxRange(r)];
result = [[self valueForKey: key] valueForKeyPath: path];
}
to /do the right thing/... I'm still working on that.
As that code fragment is essentially what I thought *was* doing the right
thing, and all my changes follow that pattern.
What is it that you think this is doing wrong?
As far as I can see, this pattern isolates all the handling of the special
'@' prefixed keys into the overridden methods in NSArray, NSSet and
NSDictionary... which seems a clean solution.
Am I missing something?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?22565>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
