|
From: Roger H. <rog...@mi...> - 2004-06-25 12:30:51
|
On Friday, June 25, 2004, at 12:21 am, James W. Walker wrote: > 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. Its never been a problem for me either. Views and Picks are used in very specific places. I would be happy if they did not inherit from Q3Object at all. > 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. I agree. > 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. Yes I think this is possible, though I don't really see the need except to make Quesa easier to understand. I doubt it could possibly cause anyone a problem as code using them already will not call Q3Shared_GetReference and hence it doesn't matter which copy of the pointer they call Dispose on. |