[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: KeyValueCoding compatibility issues
From: |
Richard Frith-Macdonald |
Subject: |
Re: KeyValueCoding compatibility issues |
Date: |
Thu, 29 Nov 2007 20:58:36 +0000 |
User-agent: |
GNUMail (Version 1.2.0) |
On 2007-11-29 17:24:55 +0000 Marcus Müller <address@hidden> wrote:
> 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.
Great ... thanks very much ... I checked the patch over visually, ran the
testsuite on a copy of base with it applied, and comitted it to svn.
- KeyValueCoding compatibility issues, Marcus Müller, 2007/11/29
- Re: KeyValueCoding compatibility issues,
Richard Frith-Macdonald <=
- Re: KeyValueCoding compatibility issues, Richard Frith-Macdonald, 2007/11/30
- Re: KeyValueCoding compatibility issues, David Ayers, 2007/11/30
- Re: KeyValueCoding compatibility issues, Richard Frith-Macdonald, 2007/11/30
- Re: KeyValueCoding compatibility issues, Marcus Müller, 2007/11/30
- Message not available
- Re: KeyValueCoding compatibility issues, David Ayers, 2007/11/30