Re: reference counting

[James W. W. <ja...@wr...>]

"Joseph J. Strout" <jo...@st...> wrote:

>So you really have to do this before you know whether to call
>Q3Shared_GetReference on a generic TQ3Object?  Does this seem
>desirable to anyone, or do we only do it that way because it's how
>QD3D worked?
>
>Given the quality of the QD3D API in general, this seems like a
>surprisingly onerous flaw, so I guess I still hope that I'm missing
>something.

It has never seemed onerous to me.  I always know which objects are 
picks or views, I don't have them floating around among other objects.

It would be dangerous to just make Q3Shared_GetReference return the 
value it was passed for a non-shared object.  Then you might think 
you'd be free to dispose the "new" reference.

It might not be bad to make the view and pick types shared, though 
it's conceivable that some program out there relies on the fact that 
they are not.
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>