[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua Digest, Vol 174, Issue 1
- From: Mike Zraly <mzraly@...>
- Date: Mon, 28 Sep 2009 10:59:17 -0400
On Mon, Sep 28, 2009 at 7:47 AM, <email@example.com> wrote:
Date: Sun, 27 Sep 2009 13:45:26 -0400
From: Norman Ramsey <firstname.lastname@example.org>
Subject: Re: Lua for large apps (was: Lua for GUI toolkit wrapping?)
To: Lua list <email@example.com>
> Static typing and compile-time checks (including warnings to the max) are
> indispensable. The alternative for dynamically typed languages are
Actually another quite respectable alternative is program analysis.
I ran into Kostis Sagonas at the airport and it seems he has had some
very good results using something he calls 'success types' for Erlang
programs. I would love to see similar technology applied to Lua.
A paper is at
Actually, it might be an interesting idea to provide an interface to set (some) and get (all)
information about a function object within the lua language itself. One might use this to
expose annotations like type assertions, comment strings, and perhaps even more low-level
information like the function's name and source location and whether or not the function calls
Couple with access to the calling function object, and transitively to the entire call stack,
one might be able to do some interesting things at runtime.