lean2/tests/lean/lua3.lean

Import Int.
Variable x : Int

(**
dofile("script.lua")
**)
chore(builtin): rename nat, int and real modules to Nat, Int and Real. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2014-01-01 21:52:25 +00:00			`Import Int.`
feat(lua): add lua_exception for wrapping lua errors, and improve Lua error messages in the Lean frontend Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-07 23:19:26 +00:00			`Variable x : Int`

feat(lua): use ( ... ) instead of {{ ... }} for nested Lua scripts The token }} is a bad delimiter for blocks of Lua script code nested in Lean files. The problem is that the sequence }} occurs very often in Lua code because Lua uses { and } to build tables/lists/arrays. Here is an example of Lua code that contains the sequence }} t = {{1, 2}, {2, 3}, {3, 4}} In Lean, (* ... ) is used to create comments. Thus, (* ... **) code blocks will not affect valid Lean files. It also looks reasonably good. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 00:05:46 +00:00			`(**`
feat(lua): add lua_exception for wrapping lua errors, and improve Lua error messages in the Lean frontend Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-07 23:19:26 +00:00			`dofile("script.lua")`
feat(lua): use ( ... ) instead of {{ ... }} for nested Lua scripts The token }} is a bad delimiter for blocks of Lua script code nested in Lean files. The problem is that the sequence }} occurs very often in Lua code because Lua uses { and } to build tables/lists/arrays. Here is an example of Lua code that contains the sequence }} t = {{1, 2}, {2, 3}, {3, 4}} In Lean, (* ... ) is used to create comments. Thus, (* ... **) code blocks will not affect valid Lean files. It also looks reasonably good. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 00:05:46 +00:00			`**)`