Re: GSIMap

2011-06-25 Thread Richard Frith-Macdonald
On 25 Jun 2011, at 08:56, Helge Hess wrote: > On Jun 10, 2011, at 6:14 AM, Richard Frith-Macdonald wrote: >> is pretty much unique to you I think > > I was also assuming that -retain can return a different object. Otherwise it > should be void (aka AddRef()) ... I'm all in favour of defensive

Re: GSIMap

2011-06-25 Thread Nat!
Am 25.06.2011 um 09:56 schrieb Helge Hess: > On Jun 10, 2011, at 6:14 AM, Richard Frith-Macdonald wrote: >> is pretty much unique to you I think > > I was also assuming that -retain can return a different object. Otherwise it > should be void (aka AddRef()) ... > The NSObject Protocol documen

Re: GSIMap

2011-06-25 Thread Helge Hess
On Jun 10, 2011, at 6:14 AM, Richard Frith-Macdonald wrote: > is pretty much unique to you I think I was also assuming that -retain can return a different object. Otherwise it should be void (aka AddRef()) ... hh ___ Gnustep-dev mailing list Gnustep-de

Re: GSIMap

2011-06-16 Thread Jens Ayton
On Jun 10, 2011, at 15:23, David Chisnall wrote: > > In that case, someone should tell Apple: as I said in the original post, this > contract is not honoured by all of their classes. Both Apple, and > LanguageKit's closure implementations return a different object in response > to -retain if t

Re: GSIMap

2011-06-10 Thread Richard Frith-Macdonald
On 2 Jun 2011, at 10:40, David Chisnall wrote: > > On 2 Jun 2011, at 06:28, Richard Frith-Macdonald wrote: > >> >> On 1 Jun 2011, at 23:48, David Chisnall wrote: >> >>> >>> This is actually wrong in retain / release mode (-retain is not guaranteed >>> to return self), >> >> The guarantee i

Re: GSIMap

2011-06-10 Thread David Chisnall
On 10 Jun 2011, at 14:14, Richard Frith-Macdonald wrote: > > On 2 Jun 2011, at 10:40, David Chisnall wrote: > >> >> On 2 Jun 2011, at 06:28, Richard Frith-Macdonald wrote: >> >>> >>> On 1 Jun 2011, at 23:48, David Chisnall wrote: >>> This is actually wrong in retain / release mod

Re: GSIMap

2011-06-02 Thread David Chisnall
t;>>> Hi, >>>> >>>> I'm trying to make NSHashTable / NSMapTable use the correct read / write >>>> barrier functions in GC mode, but I don't really understand the GSIMap >>>> code. Does it define macros for reading / writing pointers anywher

Re: GSIMap

2011-06-01 Thread Richard Frith-Macdonald
ct read / write >>> barrier functions in GC mode, but I don't really understand the GSIMap >>> code. Does it define macros for reading / writing pointers anywhere? In >>> GC mode, we need to call the relevant read and write barrier functions for >>> as

Re: GSIMap

2011-06-01 Thread David Chisnall
On 1 Jun 2011, at 23:20, Richard Frith-Macdonald wrote: > > On 1 Jun 2011, at 19:30, David Chisnall wrote: > >> Hi, >> >> I'm trying to make NSHashTable / NSMapTable use the correct read / write >> barrier functions in GC mode, but I don't real

Re: GSIMap

2011-06-01 Thread Richard Frith-Macdonald
On 1 Jun 2011, at 19:30, David Chisnall wrote: > Hi, > > I'm trying to make NSHashTable / NSMapTable use the correct read / write > barrier functions in GC mode, but I don't really understand the GSIMap code. > Does it define macros for reading / writing pointers any

GSIMap

2011-06-01 Thread David Chisnall
Hi, I'm trying to make NSHashTable / NSMapTable use the correct read / write barrier functions in GC mode, but I don't really understand the GSIMap code. Does it define macros for reading / writing pointers anywhere? In GC mode, we need to call the relevant read and write barrier