[bug #22565] EOKeyValueCoding: Support modern Cocoa KVC semantics for NSArray aggregate functions

[David Ayers]

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:
implementation

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: 

displayGroup.allObjects.@sum.value

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

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.

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

Cheers,
David

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:

  <http://savannah.gnu.org/bugs/?22565>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/