



3.3.4.1.3 Generic LuaCOM objects
When dealing with generic LuaCOM objects, the binding adopts a different policy: all Lua parameters are converted to COM ones as ``in-out'' parameters. LuaCOM assumes that these methods always return a value; if the called method does not return anything, LuaCOM pushes a nil value3.2. As all parameters are set as ``in-out'', all of them will be returned back to Lua, modified or not by the called method.
Fabio Mascarenhas de Queiroz 2005-01-07