lua-users home
lua-l archive

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

The generation of code from the protocol description isn't driven by a
fear of the efficiency of Lua.  It's driven by the fact that I don't
think Lua is going to be running on a 8-bit Freescale HCS08
microcontroller running at 24MHz anytime soon.  And the larger
platform the C code targets is a ColdFire that has about 16k of RAM
left over and about twice that in ROM.  Yes, I'm one of those embedded
systems guys who hangs out in this mailing list to remind everyone
that while Lua can go lots of places, it can't go everywhere.

 

Those are a little small for embedded Lua, but I think the ColdFire is well within the realm of possibility.  But, you're right, native code is still your best bet for those two.  I'm an embedded systems guy as well, and I've used eLua previously.  I assume you've read this thread about eLua on a ColdFire?

 

FWIW, I have embedded Lua into a ColdFire. The product ran four Lua instances under separate MicroC-OS tasks. It worked quite well, but we did have to be careful on memory usage – I believe the whole system had 512K RAM available.


______________________________________________________________________
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, reading and archival by Watlow. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Watlow accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment.

Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Watlow.