



3.2.1.0.1 Caution
LuaCOM only tracks references to COM objects. It does not work with the concepts of ``application'', ``component'', ``process'' etc. It does not know even which objects are part of the same component or application. This has some consequences on the object disposal:
- a component may only consider as ``finished'' its relationship with LuaCOM when all references to its objects are released, not only the one created with CreateObject;
- some components have a ``Quit'' method. This may close the component's interface, but it could remain running if there are any references to it. Nevertheless, these references cannot be reliably used after the ``Quit'' method has been called. To release the component, one must assign nil to all references to the component (and its sub-objects) and then call collectgarbage.
Fabio Mascarenhas de Queiroz 2005-01-07