Re: RFC Distributed Object behavior for pointers

[David Ayers]

Wim Oudshoorn wrote:

> BTW.  Do you still want me to check the behaviour on OpenStep?
> Regardless of the outcome I would vote for the autorelease
> solution.
>  
Just for the record... OPENSTEP Enterprise...

char *str;

newPool = [NSAutoreleasePool new];
str = [proxy methodRetrurningACString];
fprintf (stderr,"str:%s\n", str);
[newPool release];
fprintf (stderr,"str:%s\n", str);

shows:

str:someString
str:²§

that the value of str was invalidated.

So were not just consistent but also compatible.

Cheers,
Dave

PS; Oh, and I also vote for autorelease ;-)