RE: Precompiled multiplatform code (ARMxPC)

["Saulo Tauil" <saulot@...>]

The terminals have little memory, low cpu clock and lack of space.

The portability of uncompiled code is a security issue too, since I want
avoid code manipulation by third party. Initially this precompiled code will
be remotely transferred to the terminals.

Thanks,
Saulo

-----Original Message-----
From: lua-bounces@bazar2.conectiva.com.br
[mailto:lua-bounces@bazar2.conectiva.com.br] On Behalf Of Sam Roberts
Sent: sexta-feira, 7 de agosto de 2009 18:00
To: Lua list
Subject: Re: Precompiled multiplatform code (ARMxPC)

On Fri, Aug 7, 2009 at 10:52 AM, Saulo Tauil<saulot@muitofaciltec.com.br>
wrote:
> Thank you very much.
>
> What if I make changes in Lua to do automatic big/little-endian
conversions,
> some type redefinitions (size_t=>ulong) and disable double operation.
Would
> it be possible?
> The automatic conversion may slowdown my app, but would bring an
invaluable
> feature.
>
> I'm looking for a way to run a lightweight customizable interpreter in
> several terminals. The compiled script interchangeability would be a very
> good thing.
> Does Lua fit to my needs?
> Some advice?

Its not clear to me, at least, why you are trying to precompile.

Your lua on the ARM device has the ability to accept lua code in text
form if you are using it as an interpreter.

So why do you want to precompile lua to bytecode on your workstation,
and then transfer the bytecode to the target ARM device? Uncompiled
lua code is the most portable form of a lua program.

The standard reason to want to put precompiled code on a device is
because the lua core has been hacked to remove the parser/compiler, so
it lacks the ability to compile lua itself. Doing this saves code
space on embedded devices. This doesn't seem to be your case.

Cheers,
Sam