lua-users home
lua-l archive

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

Yes, of course Killa is my personal project right now and it's not
ready for game production,
if we plan to make games with Killa we'll probably start from zero.
There are no Lua libraries I think we would not live without or
translate and I want to add classes in the future.

Abut the zero index it's not complete in Killa right now (strings are
still base 1!)
but it can be returned to base 1 with a define if wanted.
To ease the pain of translating existing Lua code I added warnings to
potentially dangerous functions like table.insert(t, index), etc.

On Wed, May 2, 2012 at 9:11 PM, Miles Bader <> wrote:
> "[ex]" <> writes:
>> indeed my studio was evaluating to use a game engine that used it as
>> a scritpting language. Two things, the source code is very different
>> to Lua and integrating it in an engine that already uses Lua is not
>> so simple, I'm not saying it's difficult to integrate Squirrel, just
>> saying it's different to Lua. Killa can be embedded in game engines
>> that already support Lua with minimal effort
> If that's your intent, the difference in array indexing (0-based
> vs. 1-based) in Killa seems likely to cause heartache...
> That's why simple syntax changes ({ } vs. end, "self" vs. "this", etc)
> seem _far_ more innocuous than semantic changes (array indices):
> restricting yourself to the former would allow a vastly greater amount
> of re-use of existing Lua infrastructure -- libraries, both C and Lua
> [could have multiple frontends to handle the latter], binding
> generators, etc -- but once you start changing semantics, you're
> pretty much on your own...
> -miles
> --
> I'm beginning to think that life is just one long Yoko Ono album; no rhyme
> or reason, just a lot of incoherent shrieks and then it's over.  --Ian Wolff

<DESIGN... don't DEBUG!!>