Re: question regarding explicit exception in NSKeyValueCoding.m:429 -[NSObject(KeyValueCoding) setValue:forUndefinedKey:]

[Sebastian Reitenbach]

Hi Helge,
 
On Friday, July 29, 2011 07:38 CEST, Helge Hess <helge.hess@opengroupware.org> 
wrote: 
 
> On Jul 28, 2011, at 11:15 AM, Sebastian Reitenbach wrote:
> > Well, besides you said silently discarding the missing key error is maybe 
> > not the right way, putting an exception handler around the _setValue() 
> > helped...
> 
> That the missing key is consumed is actually right in this particular case. 
> And yes, for the non-libFoundation variant, you would probably need to wrap 
> it in an exception handler to accomplish the desired behavior. The SOPE 
> WOKeyPathAssoc is(was?) highly optimized for libFoundation, I think the 
> Cocoa/GS branches default to the standard KVC (it'll be muuuuch slower, but 
> that might be perfectly fine on modern hardware ;-).

I opened a bug report in the SOGo bugzilla, adding my version of the solution, 
using an exception handler. Sergey Golovin also pointed me to this old bug 
report where he implemented the missing methods in a category:
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1990

So also added this patch to the SOGo bugzilla, hope with one of these solutions 
they will be fine.

thanks
Sebastian

> 
> hh
>