Lua code compilation

简介:
Lua 虽然是脚本解释语言, 在运行前需要预编译, 同时lua还支持代码预加载操作, 预编译操作等. 
在lua代码中  1. 使用load可以将文本转换成匿名函数,  2. 使用loadfile可以将外部文件转换成匿名函数. 3. 匿名函数可以赋予给一个变量然后调用, 或者直接使用()调用.
> a=1
> load("a=a+1 print(a)") ()
2
> f=load("a=a+1 print(a)")
> f()
3


load("a = a+1")
效果"等同"于
function () a = a+1 end

但实际上是有差别的,  1. load的效率远低于直接定义函数,  2. 另外, LOAD是有全局环境.
例如 : 
> do 
>> a = 100
>> local a = 1
>> f1 = function () a=a+1 print("1:" .. a) end
>> f1()
>> f2 = load("a=a+1 print(a)")
>> f2()
>> end
1:2  -- f1输出本地变量的值
101  -- f2输出全局变量的值


注意, load和loadfile期望文本为chunk内容, 如果是表达式的话, 可在表达式前添加return返回表达式的值. 
例如 : 
> f = load("a")
> print (f)
nil
> f()
stdin:1: attempt to call global 'f' (a nil value)
stack traceback:
        stdin:1: in main chunk
        [C]: in ?
改成 : 
> f = load("return a")  -- 返回表达式的值
> f()
> print(f())
nil


load和loadfile只是预加载代码, 并不会执行它, 只有执行了这个匿名函数后, 里面的代码才会得以执行. 
例如 : 
> f1 = load("f2 = function() a=99 print(a) end")
> f2()  -- 直接调用f2是不行的, 因为f1还没有执行.
stdin:1: attempt to call global 'f2' (a nil value)
stack traceback:
        stdin:1: in main chunk
        [C]: in ?
> f1()  -- f1被调用后, f2函数就存在了.
> f2()
99
> f3 = load("b=0")  -- b的定义同样要在f3函数调用后才会被执行
> print(b)
nil
> f3()
> print(b)
0

load和loadfile不检查文本的内容, 如果非法的话, 返回nil, 同时输出错误信息.
> print(load("err"))
nil     [string "err"]:1: syntax error near <eof>
> f = load("err")
> print(f)
nil

使用assert函数可以判断load和loadfile加载的内容是否正确(是否为nil), 如果为nil的话, 返回错误.
详见末尾assert的介绍.

> assert( load("err") )
stdin:1: [string "err"]:1: syntax error near <eof>
stack traceback:
        [C]: in function 'assert'
        stdin:1: in main chunk
        [C]: in ?

如果正确则返回参数值(匿名函数)
> f = assert( load("a=1 print(a)") )
> print(f)
function: 0x204eae0
> f()
1


> assert(nil)
stdin:1: assertion failed!
stack traceback:
        [C]: in function 'assert'
        stdin:1: in main chunk
        [C]: in ?
> assert(nil,"nihao")
stdin:1: nihao
stack traceback:
        [C]: in function 'assert'
        stdin:1: in main chunk
        [C]: in ?
> = assert(1,"nihao")
1       nihao
> a = assert(1,"nihao")
> print(a)
1


dofile是对loadfile封装后调用这个匿名函数 : 
function dofile (filename)
  local f = assert(loadfile(filename))
  return f()
end


> do
>> print ("enter function to be plotted (with variable 'x'):")
>> local l = io.read()
>> local f = assert(load("local x = ...; return " .. l))
>> for i=1,20 do
>>   print( string.rep("*", f(i)) )
>> end
>> end
enter function to be plotted (with variable 'x'):
x  -- 输入x
*
**
***
****
*****
******
*******
********
*********
**********
***********
************
*************
**************
***************
****************
*****************
******************
*******************
********************

string.rep($1, $2) 将$1复制$2遍. 如string.rep("*", 10) 复制星号10遍.

load可以使用reader函数作为参数, 从reader函数读取输入, 直到输入为nil.
例如load(io.lines(filename, "*L"))
这里的io.lines(filename, "*L") 返回一个reader函数, 调用这个函数从文件中每次读取1行.
load使用reader函数作为参数时, 从reader输入直到nil.
所以 load(io.lines(filename, "*L")) 和 loadfile("filename")效果是一样的.

参考 : 

load (ld [, source [, mode [, env]]])

Loads a chunk.

If ld is a string, the chunk is this string. If ld is a function, load calls it repeatedly to get the chunk pieces. Each call to ld must return a string that concatenates with previous results. A return of an empty string, nil, or no value signals the end of the chunk.

If there are no syntactic errors, returns the compiled chunk as a function; otherwise, returns nil plus the error message.

If the resulting function has upvalues, the first upvalue is set to the value of env, if that parameter is given, or to the value of the global environment. (When you load a main chunk, the resulting function will always have exactly one upvalue, the _ENV variable (see §2.2). When you load a binary chunk created from a function (see string.dump), the resulting function can have arbitrary upvalues.)

source is used as the source of the chunk for error messages and debug information (see §4.9). When absent, it defaults to ld, if ld is a string, or to "=(load)" otherwise.

The string mode controls whether the chunk can be text or binary (that is, a precompiled chunk). It may be the string "b" (only binary chunks), "t" (only text chunks), or "bt" (both binary and text). The default is "bt".

loadfile ([filename [, mode [, env]]])

Similar to load, but gets the chunk from file filename or from the standard input, if no file name is given.

assert (v [, message])

Issues an error when the value of its argument  v  is false (i.e.,  nil  or  false ); otherwise, returns all its arguments.  message  is an error message; when absent, it defaults to "assertion failed!"
相关文章
mod_lua.cpp:37:10: fatal error: lua.h
mod_lua.cpp:37:10: fatal error: lua.h
70 0
编译x264出现错误:No working C compiler found.
编译x264出现错误:No working C compiler found.
260 0
configure: line syntax error near unexpected token `win32-dll'
configure: line syntax error near unexpected token `win32-dll'
270 0
relocation R_X86_64_PC32 against symbol lua_newstate can not be used when making a shared object
relocation R_X86_64_PC32 against symbol lua_newstate can not be used when making a shared object
207 0
|
Perl
ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1
ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1
578 0
|
Android开发 Kotlin
kotlin协程库报错“Program type already present”解决
最近在学习kotlin,学习到协程库这一块了,针对Android的话就是coroutines-android库。本来学习就不容易了,再加上kotlin现在还处于快速变化期,那个酸爽简直了,废话不多说,进入正题。
|
Android开发
1--debug时安卓源码不一致问题--Source code does not match the bytecode
AS--debug时:Source code does not match the bytecode 解决方案:保持模拟器与编译版本一致,即: 编译版本与运行版本一致
3148 0
|
设计模式