lua-users home
lua-l archive

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

On Mar 30, 2014, at 11:29 PM, steve donovan <> wrote:

> On Sun, Mar 30, 2014 at 10:20 PM, Peter Melnichenko
> <> wrote:
>> Static analysis solutions don't slow the program at all, there is no need to worry whether the all code are executed when testing, and assigning a global, if needed, is simply `_G.key = value`.
> I'm also a fan of static analysis, although I use the classic bytecode
> analysis approach (lglob).  It's been so useful that I bind my
> 'compile' shortcut key to lglob for Lua.  A hundred or so milliseconds
> later I know where my typos are, before even trying to run the
> program.

Agreed. If it were me I’d prefer an editor/analyzer/compiler solution to one involving run-time overhead (though, of course, in many cases “compile time” is part of “run time” for many Lua scripts, but you know what I mean).