[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: luac and dumping code
- From: Daniel Silverstone <dsilvers@...>
- Date: Sat, 6 Oct 2001 00:10:47 +0100
I am working on a design for a persistent system which interprets lua files.
In order to effect a speedup, I want to cache the compiled lua Proto
objects. It seems to me that the best way to do this is to dump them (like
luac does) and then keep the dump around in memory so I can undump it into
any of the lua states I want, whenever I want to. However I have hit a snag.
Looking through the luac code (E.g. strip() which I do want to be able to
do) it just sets bits of the Proto objects to be NULL -- will lua garbage
collect the stuff which is then orphaned, or is this memory lost to the
general mess of things?
I need to know, because if this would introduce a memory leak, I need to
address the issues :)
Many thanks in advance.
Daniel Silverstone http://www.digital-scurf.org/
Hostmaster, Webmaster, and Chief Code Wibbler Digital-Scurf Unlimited
GPG Public key available from germany.keyserver.net KeyId: 20687895
With listening comes wisdom, with speaking repentance.