Re: NSInvocation does not seem to always assign return value (suite)

[Sebastien Pierre]

Hi Richard,

On Tue, 22 Apr 2003 16:41:22 +0100
Richard Frith-Macdonald <richard@brainstorm.co.uk> wrote:

> If adding/removing the assertions changes the code behavior, the most 
> likely problem is actually with uninitialised variables having 
> different values depending on how the code was compiled.
> 
> Unfortunately I can't help beyond that ... your code snippet and 
> explanation leave a lot unclear to me  ....
> 1. when returning an object, you release pool, which might release 
> invocation, which might release the object before you return it.

After some more investigations (and luck), this was exactly the root of the 
problem. Do you know any good explaination on how exactly the NSAutoreleasePool 
works ?

Thanks,

 -- Sebastien