Re: DO question.
Re: DO question.
- Subject: Re: DO question.
- From: Jonathan Wight <email@hidden>
- Date: Tue, 02 Apr 2002 00:18:22 -0600
On 04/01/2002 15:43, "Jonathan Wight" <email@hidden> wrote:
>
> IIRC, it *is* byref, but property list classes were sent bycopy for higher
>
> effectivity.
>
>
>
> I can't find the appropriate documentation excerpt anymore though?!?
>
>
Well that may explain the problem I'm seeing... My classes are laid out
>
kinda like this:
>
>
@interface CAttributes {
>
NSMutableDictionary *mContainer;
>
}
>
@end
>
>
@interface CDaemon {
>
CAttributes *mAttributes;
>
}
>
- (CAttributes *) getAttributes;
>
>
The CDaemon is being shared and the client is calling getAttributes and
>
performing get/set operations upon the object. If I dump the attributes out
>
on the client I see the changes I made but when I dump them out on the
>
daemon I don9t see them at all.
>
>
So how do I fix this? I've changed the getAttributes to be byref and this
>
didn't seem to do diddly.
More information and this is even weirder...
I added this function to the daemon (and it's protocol of course):
- (byref void)getAttributes: (inout Cattributes **)outAttributes
{
*outAttributes = [self attributes];
}
Well the long and the short of it is calling when the daemon enters this
function (called from the client of course) and sets outAttributes the
daemon just hangs and the client sits there waiting for a response...
Seems like I just can't get my damn attributes from the server by
reference... Argh! (Yeah I'm checking the pointer passed in and it is
valid).
Anyone seen anything like this before?
I'm really beginning to go insance from this one...
Cheers.
Jon.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.