lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


Rob Kendrick wrote:
On Tue, 11 Aug 2009 00:39:00 +0800
KHMan <keinhong@gmail.com> wrote:

Rob Kendrick wrote:
On Mon, 10 Aug 2009 13:29:18 -0300
"Saulo Tauil" <saulot@muitofaciltec.com.br> wrote:

The terminals have little memory, low cpu clock and lack of
space.
Given that compiled Lua is often /larger/ than the source, you may
find that leaving the compiler in and gzipping and/or using
something like LuaSrcDiet saves more space, depending on your exact
circumstances.
I think he means one of those lower-end 32-bit ARMs. They probably have about 8-32KB internal SRAM. Everything runs on-chip, and the program memory can probably be protected. You can upload your programs as firmware, with a bootstrapper that can probably include some sort of security encryption. Can't really do the compilation or interpretation front-end on-chip.

There are at least two broad kinds of ARM MCUs, and I don't believe Saulo is talking about the kind that can run Linux.

We're in broadly the same situation.  Although I'd never actually
consider Lua for anything with as little as 32kB of RAM.  Of course,
compiled code would come out of your Flash budget, anyway.

Yeah, I agree, I wouldn't do it myself either, I would also want memory usage to be very strictly determined. I guess Bogdan Marinescu's eLua, if it has not been mentioned already, is something the OP can scope out.

--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia