[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lua-l
Subject:    Re: Execution of pre compiled lua code from memory mapped files
From:       Jay Carlson <nop () nop ! com>
Date:       2015-05-29 15:01:53
Message-ID: F541E62A-65F4-4DCA-A25F-54303DB18A64 () nop ! com
[Download RAW message or body]

On 2015-05-29, at 10:24 AM, Luiz Henrique de Figueiredo <lhf@tecgraf.puc-rio.br> \
wrote:
> 
> > I'm confused.  Although not part of the core library, luaL_loadbufferx()
> > exists, and is implemented in a very small amount of code:
> 
> The point is that when Lua loads precompiled Lua code, it *copies* the
> data to its internal data structures.
> 
> The question is about how to avoid this copy, especially in RAM
> starved systems, when precompiled code is already stored in ROM.

For people just joining in, check out \
http://www.eluaproject.net/doc/v0.9/en_arch_ltr.html for a discussion of what eLua \
does already.

I ran into the problem in my Lua-FLTK days (4.0, 2001?), where my tolua binding \
created one table per class for its methods. Not very memory-friendly, and the data \
structures were not sharable across Lua invocations the way C shared libraries can \
be.

Jay


[prev in list] [next in list] [prev in thread] [next in thread]