5.1 Limitations

Here are listed the current limitations of LuaCOM, as of the current version, and information about future relaxation of this restrictions.

• LuaCOM currently supports only exposes COM objects as ``single use'' objects. That might be circumvented by exposing many times the same object. This restriction might be removed under request;

• there is no ``UnRegisterObject'' method yet. Objects registered with RegisterObject must be removed from the registry manually (or using another tool); this is due to the next release;

• LuaCOM doesn't support COM methods with variable number of parameters. This could be circumvented passing the optional parameters inside a table, but this hasn't been tested. This may be implemented under request;

• there isn't support for converting tables that are not ``array-like''. This may be relaxed in a future version, depending on the feasibility;

• LuaCOM only allows one connection point for each ActiveX object. This limitation may be relaxed in future versions;

• LuaCOM doesn't provide access to COM interfaces that doesn't inherit from IDispatch interface. That is, only Automation Objects are supported. This restriction is due to the late-binding feature provided by LuaCOM. It's possible to provide access to these COM interfaces via a "proxy" Automation Object, which translate calls made through automation to vtable (early-binding) calls. It's also possible to implement this "proxy" directly using LuaCOM C/C++ API, but this hasn't been tested nor tried;