Footnotes

LuaCOM

previous page next page

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.

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

... ``set''^3.1

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

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

... value ^3.2

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.

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

... fields ^6.2

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

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

previous page start next page