[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: bit.lshift and performance - luabitop v.s. lua-5.2.0-work4
- From: KHMan <keinhong@...>
- Date: Wed, 13 Oct 2010 21:16:28 +0800
On 10/13/2010 8:52 PM, Bogdan Marinescu wrote:
On Wed, Oct 13, 2010 at 3:40 PM, Enrico Colombini wrote:
On 13/10/2010 14.12, KHMan wrote:
Anyway most app developers do not need to code DCTs and FFTs nowadays.
Mostly true, but last time I worked in game development I also wrote tools.
I used Lua whenever possible to save time and effort, but even for simple
image file manipulation I often had to resort to C/C++.
I remember having to write horrible Lua bit ops workarounds just to be able
to make small changes to data files.
I can understand this all too well. Bit operations in Lua are a real
PITA for anything that's not trivial, and I felt that a lot in eLua.
On embedded systems, doing bit operations is many times a necessity,
especially when writing low-level code that "talks" directly to the
hardware (and having to manipulate lots of registers at bit level in
the process). I'm seriously considering adding one of the bitwise
operators patch from the Lua power patches page to fix this, even at
the price of loosing full compatibility with standard Lua.
I agree with that. If there is a lot of bit ops, I think there is
a good case to bite the bullet and use bitwise operators. I would
want that too on an embedded system.
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia