--- In [email protected], "brucexs" <bswit...@...> wrote: > > > > > I could in principle release the just-used handle > > when callback is re-entered (reading current contents of the variable > > obj/objFile and releasing handle therein). But I can imagine situatios > > where that would be a no-no (maybe user is populating > > a vector with elements of a collection). > Here is a related situation. What happens if a user does this: > > Function AKA > local x = create an object with com > global xAliased = x > quit > > > Will local x be released, meaning xAliased is a dangling reference?
Yes. > If so, then for consistency, you should release objFile and warn people about > aliasing (of course, it would be better to use reference counting features of > PowerPro which would tell you about assignment, but I think you tried these > and find them buggy and I don't want to try to debug this feature at this > time). Yeah, reference counting would be good. Let me know if you ever want to play with it again. > > Problem at the moment is that com.release_all and com.unload > > freeze immeidately after above loop. They work okay after a short delay. > > I'll do some more debugging next week. > > Objects are just tired and need a rest, most likely. Yeah, and there may be a bit of prtest about loss of individual identy, now merely being referred to as one of...each. May have to unruffle some feathers.
