Hi, John Labenski ha scritto: > First off, I'm going to rename some rather unfortunately named > functions. These are mostly internal to wxLua, but you may have to > rebuild your bindings using genwxbind.lua. > > More importantly, do we want stricter function parameter type > checking. Lua itself is very generous and will convert numbers to > strings, nil to number, etc... BUT, this means that without some > checking you can spend a lot of time debugging a small typo since vars > can be created on the fly with the value nil. even if honestly I still haven't found enough time to start using wxLua myself :(, just a dummy advice: I'd keep the auto conversion code (it's an important part of modern interpreted languages I think) but I understand what you mean - so maybe we could add a work mode to wxLua interpreter so that it logs the creation of each new variable (to help debugging). This sort of logging has the disadvantage however that the log may become extremely long and thus unusable for big programs.
BASIC (I started programming with it ;)) had an "Option Explicit" statement which allowed to turn on & off at run-time the creation of the variables on the fly: http://msdn2.microsoft.com/en-us/library/y9341s4f(vs.80).aspx maybe something like that could be the solution... Francesco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
