KeyValueCoding compatibility issues

[Marcus Müller]

Hi List,

KVC compatibility is badly broken in several situations, where  
subclasses usually override specific methods, but the calling API was  
partly ported to use the new-style KVC, i.e. -takeValue:forKey:  is  
somehow mixed with -setValue:forKey:. Usually, this happens when you  
port an application to the new API but some underlying framework has  
yet to be ported... the result is something which doesn't work  
properly at all.

Attached, find a patch that fixes all these problems. As an added  
bonus, all compatibility code is prepared for exclusion from  
compilation, making it very easy to actually migrate to the new-style  
KVC completely. All compatibility workarounds will then be excluded as  
well, making KVC a bit faster altogether.

kvc-proper-compat-v3.diff
Description: Binary data

Cheers,

  Marcus

--
Marcus Mueller  .  .  .  crack-admin/coder ;-)
Mulle kybernetiK  .  http://www.mulle-kybernetik.com
Current projects: http://www.mulle-kybernetik.com/znek/