[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #22565] EOKeyValueCoding: Support modern Cocoa KVC semantics for NS

From: David Ayers
Subject: [bug #22565] EOKeyValueCoding: Support modern Cocoa KVC semantics for NSArray aggregate functions
Date: Wed, 12 Mar 2008 17:37:03 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20080129 Iceweasel/ (Debian-

Update of bug #22565 (project gnustep):

             Assigned to:                    None => ayers                  


Follow-up Comment #1:

This is an RFC/RFA for a patch to -base to 
- implement the simplified version of valueForKeyPath: on NSArray
- get NSObject's valueForKeyPath: to call NSArray's valueForKeyPath:

This will give currently just give -base the ability to handle the "simple"
aggregate key value passing... i.e. you still do not get the the correct value
for the key path: 


but at least the NSArray will receive valueForKey:@"@sum.value"

To the requested feature I believe we need to replace the implementation of:

      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.

But would it be OK to commit this but to allow GDL2 to at least work with the
more limited WO45 KVC semantics?


The reason I didn't notice this earlier is because the testsuite only tested
the aggregate KVCPaths directly on NSArray and I haven't updated our Apps to
current GNUstep SVN for quite a while.

(file #15250)

Additional Item Attachment:

File name: kvc.patch                      Size:2 KB


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]