Hi Allen,
Allen Bierbaum wrote:
>> To go between threads you would have to use a MTRefPtr. That one behaves
>> pretty much like the current FCs: whenever it is dereferenced it returns
>> a CPtr for the current thread's aspect.
>
> These last couple points seem pretty nasty to me. Just to be clear,
> this means that I can't use RefPtr's like I do today. For example I
> can't just store a RefPtr as a member of an application object and then
> have that object call the opensg object from whatever thread it happens
> to be executing within?
No, for that you'd have to use an MTRefPtr.
> This seems like a pretty severe limitation to me. I would think we
> would want the recommended user handle (RefPtr) to "just work" in all cases.
There is overhead for that, and not many applications use it, and even
if probably not for all RefPtrs. If you want to do it you can use
MTRefPtrs everywhere and effectively get the current behavior.
> Don't RefPtr's currently work in any aspect they are used. IIRC they
> are and changing this would break most all of our applications.
Just like FCPtrs, yes, but that's the main part that's changing.
> I am using those, but I think they can be ported over very easy once the
> recommended user handle type is selected (RefPtr or whatever).
I think so.
Yours
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
