[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:
From: |
Manuel Guesdon |
Subject: |
Re[2]: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey: |
Date: |
Wed, 26 Mar 2003 15:16:38 +0100 (CET) |
On Wed, 26 Mar 2003 14:33:32 +0100 David Ayers <address@hidden> wrote:
>| Hi Manuel,
>|
>| Manuel Guesdon wrote:
>|
>| >On Tue, 25 Mar 2003 00:07:24 +0100 David Ayers <address@hidden> wrote:
>| >
>| > >| David Ayers wrote:
>| > >|
>| > >| > Should/could we implement something like GSObjCReplaceMethod(Class
>| > >| > class, struct objc_method *old, struct objc_method *new) or should
>| > >| > this be handled differently?
>| > >| >
>| > >| Hi Richard,
>| > >|
>| > >| I know this is a rather "brutal" approach (but then again so was the
>| > >| behavior suggestion), yet I believe it should work for both runtimes
>and
>| > >| be useful in similar situations. Would you consider the attached
>patch
>| > >| as acceptable? If so I would commit.
>| >
>| >This kind of method would also solve other problems, for example my
>'combined key' problem :-)
>| >
>| >
>| >
>| Well actually the problem can be solved the way it is now by leaving the
>| implementation of this special case handling for
>| valueForKeyPath:/takeValueForKeyPath: in NSDictionary as base's and (I
>| believe) Foundation don't override this in NSDictionary.
i.e. implement it in gdl2 KVC like before, right ?
It's fine for me.
>| Or do you want
>| to extend this mechanism to all (i.e. custom) objects? I can't really
>| see the usefullness of a key like "'some.key.with.periods'" for any type
>| of object except NSDictionary... But if you like, I can see if I can
>| replace NSObject's implementation for GDL2.
No, I see this usefull only for display group query dictionary. But may be
there's a better solution: we don't
overwrite/implement this for NSDictionary but we implement
takeValue:forKeyPath:,... in GSWDisplay group and this
implementation will take care of combined keys.
What do you think ?
Manuel
--
______________________________________________________________________
Manuel Guesdon - OXYMIUM <address@hidden>
14 rue Jean-Baptiste Clement - 93200 Saint-Denis - France
Tel: +33 1 4940 0999 - Fax: +33 1 4940 0998
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, (continued)
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, Richard Frith-Macdonald, 2003/03/24
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/24
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/24
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, Stéphane Corthésy, 2003/03/25
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, Richard Frith-Macdonald, 2003/03/25
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/25
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/25
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/25
- Re[2]: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, Manuel Guesdon, 2003/03/25
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/26
- Re[2]: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:,
Manuel Guesdon <=
- Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, David Ayers, 2003/03/26
Re: RFC: [GDL2/base] unableToSetNullForKey: / unableToSetNilForKey:, Manuel Guesdon, 2003/03/25