[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Lua - C interfacing [RE: Lua documentation, Python, etc.]
- From: Asko Kauppi <Asko.Kauppi@...>
- Date: Thu, 6 Jun 2002 16:31:43 +0300
I've extended the 'glua10' found at Lua's "tools" page to get better C / Lua
integration. I agree that the native tools for this are still too ...
clumsy.
My idea is to have a stand-alone "original" lua interpreter, which
automatically scans a certain "extensions" directory for any modules placed
in there by the user / admin. It'll call those modules, letting them
register with itself and voila!
This means your C code should be in DLLs. If you want to avoid them
completely, you'll need to compile a monolithic app + lua like everyone's
now supposed to be doing.
- Asko
--
Asko Kauppi
Flextronics Design Finland
Box 23, 39201 Kyröskoski, Finland
www.flextronics.com
> -----Original Message-----
> From: Pyrogon Public [SMTP:public@pyrogon.com]
> Sent: Wednesday, June 05, 2002 8:11 PM
> To: Multiple recipients of list
> Subject: RE: Lua documentation, Python, etc.
>
> To clarify, when I complain about the documentation it's mostly that I'm
> not experienced with integrating a scripting language into a core engine
> directly. The previous games I've worked on used DLLs for their
> modification and scripting, so issues like conversion between compiled
> and scripted data structures never really came up.
>
> I've read Roberto's book, but it's 4.0 only and doesn't cover 4.1, and
> most of what I see are language references or very domain specific
> tutorials, whereas what would be particularly helpful to me (and maybe
> it's just me, so take this with a grain of salt) is a tutorial that
> shows how to integrate a Lua scripting system with a C/C++ main engine
> (or vice versa).
>
> Learning Lua itself isn't that difficult, it's the integration with a
> compiled binary that's the tough part (philosophically speaking, the
> real tough part is also figuring where to draw the line between the
> two).
>
> Thanks,
>
> Brian
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.