... add-ons^2.1

``Dynamic loading of the LuaCOM library is not supported in the official distribution of LuaCOM, although some may have implemented it elsewhere.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... Lua^2.2

Notice that COM must be initialized in each thread that will use it. To use LuaCOM in this situation, it's not safe to share a single Lua state among several threads; one should create a new Lua state for each thread and then initialize LuaCOM with this state.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...methods^3.1

In version 1.1 the old API is still accessible when LuaCOM is used with Lua 4, so that code written for LuaCOM 1.0 still works with LuaCOM 1.1. It means that all functions of the API can be accessed as luacom_<function> or as luacom.<function>. This may change in the next versions, so upgrade your code as soon as possible!

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... ``set''^3.2

In a future version it might be allowed to change the prefix.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... value^3.3

This feature allows a clear distinction between the return value and the in-out parameters, as all parameters will end up being returned.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... parameters^5.1

Notice that LuaCOM does not implement named parameters; it just takes them when called from a COM client and puts them.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... fields^6.1

For a better description of these fields, see COM's documentation.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.