Re: [2/3 solved] CFMessage woe
Re: [2/3 solved] CFMessage woe
- Subject: Re: [2/3 solved] CFMessage woe
- From: Dave Keck <email@hidden>
- Date: Thu, 4 Mar 2010 04:50:14 -1000
> Back to the problem as seen at the top of the message:
> but what I don't need is a copy of my data; I don't mind a different
> CFRef as long as it points to the raw storage that I've put in.
We're running in circles, but I'm not sure who's misunderstanding who.
Let me try again:
Thread A has a CFMutableArray - myArray - that contains 5 CFStrings.
Thread A sends a message to thread B with a CFData - myData - that
encapsulates the pointer that is myArray. (Therefore on 32-bit, myData
will be 4 bytes long, whereas on 64-bit myData will 8 bytes long.)
When thread B receives this message, it will extract this pointer out
of the CFData object. Voila! Thread B now has a pointer to the exact
same myArray that thread A has. If thread A decides to add another
object to myArray, thread B will see this change to myArray, because
it's the exact same array. (This is of course neglecting the
thread-safety.)
If that all makes sense and I'm the one misunderstanding, let me know
and I'll be happy to shutup. :)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden