Easiest way (that I know of) is to put it up some place for download
(eg: luaforge) with a little bit of information and then list it on
the Lua Users Projects page (http://www.lua.org/uses.html
<http://www.lua.org/uses.html>).
I'm curious, does your update surface it as a DLL that can be required
from a standard Lua script or do you have to completely re-build Lua
to use it? Either way, I'd love to get a copy and see if it solves my
problem :).
On 7/13/07, *Dave Nichols* <dave.nichols@make247.co.uk
<mailto:dave.nichols@make247.co.uk>> wrote:
I have ported LuaCOM to 5.1 but do not know how to donate it. (I'm
not a
C programmer and Wiki's are a mystery to me). If anyone can give me an
idiots guide to giving everyone access to it I'll gladly do it.
Petr Stetiar wrote:
> Jeremy Darling <jeremy.darling@gmail.com
<mailto:jeremy.darling@gmail.com>> [2007-07-13 08:03:11]:
>
>
>> I've searched all over the web and the only library I've found
is LuaCOM,
>> but the last update was back in 2005 and it appears is for Lua
5.0. I'm
>> working in Lua 5.1 and would like something that worked as a
standard DLL
>> Module that can be plugged under Lua itself. Anyone have any
ideas on where
>> to start or if there is another way to go about this using only
the normal
>> Windows API? Sorry for the two sided question, but I'm going nuts!
>>
>
> You can either port LuaCOM to recent Lua release (consider it,
you're giving
> something back), or you can use C/Invoke[1] and use Windows
OLE/API directly.
> Similar to Python's ctypes or .Net's pinvoke().
>
> 1. http://www.nongnu.org/cinvoke/index.html
>
> -- ynezz
>
>
>
--
Regards,
Dave Nichols
Match-IT Limited
Tel: 0845 1300 510
Fax: 0845 1300 610
mailto: dave.nichols@make247.co.uk <mailto:dave.nichols@make247.co.uk>
http://www.make247.co.uk
Email Disclaimer: The contents of this electronic mail message and
any attachments (collectively "this message") are confidential,
possibly privileged and intended only for its addressee ("the
addressee"). If received in error, please delete immediately
without disclosing its contents to anyone. Neither the sender nor
its management or employees will in any way be responsible for any
advice, opinion, conclusion or other information contained in this
message or arising from it's disclosure.
--
Jeremy
"Help I suffer from the oxymoron Corporate Security."
