[erlang-questions] luerl stacktraces

[Max Lapshin]

Hi.

luerl (https://github.com/rvirding/luerl ) is a wonderful project, thanks
for it.


3 years ago Robert told that it is a big problem to add proper stacktraces
to lua errors.

Right now it is:

{lua_error,{undef_function,nil},{luerl,{array,25,100,undefined,{{{table,{array,0,10,nil,10},{{{{empty,<<"_G">>,{tref,0},empty,<<"_VERSION">>,<<"Lua
5.2">>,empty},<<"assert">>,{function,#Fun<luerl_lib_basic.1.33635960>},{empty,<<"auth_url">>,<<"
http://go.commpass.tv/flussonic/auth
">>,empty,<<"bit32">>,{tref,11},empty},<<"collectgarbage">>,{function,#Fun<luerl_lib_basic.2.33635960>},{empty,<<"comet">>,{tref,19},empty,<<"converter">>,{tref,18},empty}},<<"dofile">>,{function,#Fun<luerl_lib_basic.3.33635960>},{{empty,<<"eprint">>,{function,#Fun<luerl_lib_basic.4.33635960>},empty},<<"error">>,.....


For something like:

mytable.unexisting_function("Hello world")


Are there any severe problems to add stacktraces?

It would be very good at least to have file and line of the error to show
user where he has error.


Perhaps some library function like:  luerl_lib:unpack_stacktrace(Error) ->
... ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150112/7ceb2931/attachment.htm>